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

Open exception for (erroneously) blocked extension

Environment: SG230, UTM 9, latest patch. Web filtering in use with extension blocking.

Users have important need to visit a particular URL, which is: http://outlook.com/owa/uc.x-contoso.com They are blocked due prohibited file extension. I'm assuming that the ".com" is causing the problem.

But it doesn't go to a file. It goes to Outlook Web Access. Can verify this on an unfiltered network, there is no file.

Despite my best efforts, I am stymied to add an exception. I've created an exception for extension blocking, and used various regular expressions, without success. It always blocks on "forbidden extension". I'm beginning to think that the double ".com" has something to do with it?

Any advice here?



This thread was automatically locked due to age.
Parents Reply Children
  • Try the following, Lee:

    ^https?://[A-Za-z0-9,-]*outlook\.com/

    Or just try the complete URL from your original post.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • You know, I thought I had tried the original URL repeatedly, and it didn't work before, but now it does.

    Maybe I typo'd it previously.

    Well anyway, that was the solution! And now I can get these users off my back.

    Thanks as usual, Bob!