Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 1655 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Scan HTTPS (SSL) Traffic

jreverman
Before updating to 7.504, Enabling this setting on our filter profiles allowed us to specify filter actions for HTTPS sites.

Example: We want to block https://mail.google.com, but want to allow Https://mail.google.com/gpi.us.

By enabling the Scan HTTPs for the profile, the web proxy would enumerate the full URL and Pass or block depending on the white list.

After the update, the proxy stops enumerating at Https://mail.google.com, completely ignoring anything after the .com. 

We are running two proxies, one at 7.503 and the other at 7.504, and the older version still works as intended.

Was there a change? 

Thanks,


This thread was automatically locked due to age.
Parents
  • 0
    I don't know if it was changed or not but until you find out I would suggest you separate this into 2 filter actions/assignments and add them both to the profile but making sure the longer url is on top of the other one.
    Don't know if that works though it might be worth a try.
    Anyone with more information?
  • 0 in reply to Krycek
    Yes, this was my initial thought also. The proxy simply will not enumerate beyond the .com when in SSL.

    This setup works fine when doing regular HTTP, but that wont work for us.

    Thanks for the response.
Reply Children
No Data