Destination Site(s) Non-Standard Port

[codex]

We have a need in an Explicit Intercept environment to allow specific URLs to be reached on non-standard ports i.e. not 80/443. The connecting client will connect the the Web Gateway on its listening port, it cannot be configured to connect to another listening port based on URL. We will not be doing SSL Scanning in this deployment; how would we go about doing this?

[mkutrieba]

Hello @codex,

so if I understand correctly we talk about the URL port here and not the proxy port.

Example: Client sends request for URL https://abc.com:1234 to proxy on listener port, e.g. 9090. 

On MWG under common rules you should have a rule set called " Restrict Connect Ports" where 443 is entered in a list. Means, every connect to any port other than 443 will be blocked there.

So you just would need to enter 1234 in this list and client is allowed to connect to website on URL port 1234.

Please let me know if I have correctly understood this and if my information helps here.

[codex]

Thank you for replying.  I should have been more clear in the OP.  

The ask was for the ability for a client to connect on 443 but since the server listens on another port i.,e. 80443 the MWG would have to in a nutshell do port translation on specific URLs only.  The listening port would not have required to change. This has now become moot, but I am curious if it is possible.