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?
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.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.