Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 19765 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

Some URLs are blocked when using HTTPS Inspection

Peter Lapornik

We are facing an issue of blocked requests when using the "Decrypt & Scan HTTPS" option for certain sites.

Here is an example:

https://channel9.msdn.com/ works

https://channel9.msdn.com/blogs works (it gets redirected to https://channel9.msdn.com/Browse/Blogs )

https://channel9.msdn.com/blogs/ea.azure.com results in a blocked request

 

If we turn off the "Decrypt & Scan HTTPS" option then the blocked site works.

Regarding HTTPS Inspection, the "Block unrecognized SSL protocols" and "Block invalid certificates" options are both not selected (i.e. disabled).

We are running SFOS 16.01.3 MR-2

 

Is anyone else facing this issue? Is there a solution?



This thread was automatically locked due to age.
Parents
  • +1

    Peter,

    I am able to surf on all the 3 sites and I have SSL Enabled. It depends on what filters you have enabled. You can check why the website is blocked using the Log Viewer > Web Log Filter

    Thanks.

     

  • 0 in reply to lferrara

    Thanks to everyone that tested the URLs that I posted and were able to tell me if they worked in their environment. Good feedback can be invaluable when trying to solve issues such as this.

    After more testing we worked out that the problem was the default Not Suitable for the Office user activity. In particular, the Not Suitable for the Office user activity includes the Executable Files file type. This file type includes .com files.

    This is what was causing sites like the one I posted above to be blocked.

Reply
  • 0 in reply to lferrara

    Thanks to everyone that tested the URLs that I posted and were able to tell me if they worked in their environment. Good feedback can be invaluable when trying to solve issues such as this.

    After more testing we worked out that the problem was the default Not Suitable for the Office user activity. In particular, the Not Suitable for the Office user activity includes the Executable Files file type. This file type includes .com files.

    This is what was causing sites like the one I posted above to be blocked.

Children