Guest User!

You are not Sophos Staff.

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

HTTP Error 502 Inflation failure, invalid content when in Chrome and searching on google.ca/om

Hi Folks,

I am seeing a weird error with Chrome only since Monday morning; when trying to search (either through the bar or first navigating to google.com or .ca) I will receive a HTTP Status Code 502 Inflation failure, invalid content.

The facts so far:

  • XG210 on 15.01.0 MR-3
  • I am connecting over HTTPS
  • This does not occur in IE or Firefox. My Chrome version is 54.0.2840.71 m
  • This does not occur if HTTPS scanning is off and will not re-occur after it has been turned back on until the browser has been closed and reopened or a certain amount of time has passed. Even if I open a new tab and search after scanning has been re-enabled it will work
  • I was the first person to notice the issue but it has spread. It is not limited to one rule.
  • I am already dropping QUIC traffic
  • My patterns are all up-to-date and I last checked today at 3pm
  • I have the CA installed in my OS/Browser. Removing the CA causes the standard NET::ERR_CERT_AUTHORITY_INVALID HSTS related error.
  • Re-adding the cert freshly downloaded from the SF doesn't help
  • The clock on the Sophos is in sync with my computer
  • A packet capture via the WebUI yields no clues. It simply tells me which rule it went through but no drops/invalids etc.
  • A drop-packet-capture yields nothing

This was working perfectly fine for several weeks. I have noticed other folks with some other 502 errors (Bad Gateway, Proxy Timeout, etc.) but none of the fixes there seem to have works (i.e making sure your patterns are up to date).

Anyone have any clues or tips?

I am playing phone tag with Sophos support so I thought I'd ask here in the mean time.

 

Thanks,

Devon

 



This thread was automatically locked due to age.
Parents
  • Devon,

    I have seen this error on Firefox after the v16.01.1 where the certificate has been generated by the appliance but the old certificate was still used inside the Browser.

    What I suggest to you is to upgrade to latest version (16.01.1), download and import the CA used for Web Filtering Scan and see if the problem exists.

    v16 has a better log management and troubleshooting.

    Thanks

Reply
  • Devon,

    I have seen this error on Firefox after the v16.01.1 where the certificate has been generated by the appliance but the old certificate was still used inside the Browser.

    What I suggest to you is to upgrade to latest version (16.01.1), download and import the CA used for Web Filtering Scan and see if the problem exists.

    v16 has a better log management and troubleshooting.

    Thanks

Children
No Data