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

Instagram Exeption - Smartphone - web filtering

Hi,

i have defined an exception for Instagram.
Nevertheless I get an error message

2017:07:21-19:52:39 utm_01 httpproxy[27713]: id="0003" severity="info" sys="SecureWeb" sub="http" request="(nil)" function="read_request_headers" file="request.c" line="1581" message="Read error on the http handler 107 (Input/output error)"

Could you please help me?


Proxy is "transparent-Mode"
Firmware: UTM Release 9.500-9

Many Thanks



This thread was automatically locked due to age.
  • Try the following Google, Doug, and read the first thread:

    site:community.sophos.com/products/unified-threat-management/f SXL

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • SXL is not related.

    In fact...  I'm not even positive that non-SXL even works anymore.  It's not supported and not tested.  Turning it off and on doesn't do anything useful.

     

    What I see in the logs is:

    An HTTPS connection is made, matching the exception.  Within a split second there is a problem on the connection and the UTM drops it.

    The client retries and there is another HTTPS connection.  Repeat.

     

    What the error is, I don't know.  Do you have an upstream proxy?  Anything else that could be unusual in your setup?

    Try modifying your exception to also exclude all the SSL things.

     

     

  • I don't know, Michael.  I have that in my notes from around the time 9.3 came out, and it resolved a similar problem at the time.  What do the devs say happens in 9.502 when use_sxl_urid is 0?  Is that parameter no longer used?

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Doing those commands will cause a service called urid to restart - and it is urid that does SXL and categorization.  Potentially this would fix categorization problems, but this problem is in SSL connections being dropped randomly.

     

    As for running with use_sxl_urid 0, that switches you back to using CFFS.  The devs will say "ask Michael" and I will say we haven't tested that in years.  AFAIK we haven't done anything that would deliberately break it though.  The CFFS cloud servers that were used before SXL are still live, as UTM 9.2 (?) and earlier still connect to them.  But as we've always said - messing around in cc on your own is not officially supported.  :)  It doesn't void warranty, but we won't fix it if its broke.