We're using the SSL scanner rule set and running into issues with web development tools that use SSH over HTTPS failing, specifically to a github.com address. I have github.com in the MCP bypass list, and MWG reporting doesn't show the traffic being blocked, or allowed, so I assume the bypass is working. How does the SSL scanner rule set handle SSH over HTTPS?
Solved! Go to Solution.
Hello,
we are a HTTP/S proxy. As long as it stays as HTTPS and is bypassed from SSL scanner rule set to avoid content inspection it should work.
Once it runs into it and MWG can look inside the HTTPS session, it will detect something which it does not know and further does not know what to do with it.
So bypassing SSL scanner might work and running into SSL scanner might cause issues.
Hello,
we are a HTTP/S proxy. As long as it stays as HTTPS and is bypassed from SSL scanner rule set to avoid content inspection it should work.
Once it runs into it and MWG can look inside the HTTPS session, it will detect something which it does not know and further does not know what to do with it.
So bypassing SSL scanner might work and running into SSL scanner might cause issues.
So to summarize, the SSL Scanner rule will not recognize SSH over HTTPS and will cause problems. Thanks.
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: