W3C home > Mailing lists > Public > www-validator@w3.org > August 2015

Re: Improve can't gunzip content error

From: Michael[tm] Smith <mike@w3.org>
Date: Mon, 10 Aug 2015 12:04:57 +0900
To: Joe Merrill <jmerrill@crankingsoftware.com>
Cc: www-validator@w3.org
Message-ID: <20150810030457.GA963@sideshowbarker.net>
Hi Joe,

Joe Merrill <jmerrill@crankingsoftware.com>, 2015-08-06 10:08 -0600:
> Archived-At: <http://www.w3.org/mid/CAHeScEg3CXuxRCwr5=aOEPNKba6ivs4WxZgD70VRPPiBp9XU5g@mail.gmail.com>
> While trying to validate http://www.mdsupplies.com the following error is
> show:
> A fatal error occurred when attempting to decode response body from
> http://www.mdsupplies.com/. Either we do not support the content encoding
> specified ("gzip"), or an error occurred while decoding it.
> The error was: Can't gunzip content: Header Error: Minimum header size is
> 10 bytes

Yeah, that seems to be a bug in the legacy Markup Validator (that is,

I have no idea how to troubleshoot it. But the fix is just to not use the
legacy Markup Validator but instead to just use the current W3C HTML
Checker (https://validator.w3.org/nu/).

> The same page can be validated by the Nu validator with no errors.

Yeah https://validator.w3.org/nu/?doc=http://www.mdsupplies.com works as
expected, and that’s the recommended tool to use.

> It can also be fetched by google and displays correctly in all browsers.
> If this error could show the request/response headers it would be very
> useful. Or if it could list the actual specification(s) that the response
> is violating.

There is no problem with the response. You can verify that by doing this:

  curl -s -H "Accept-Encoding: gzip" http://www.mdsupplies.com | gunzip -t

Which as expected returns nothing (indicating there’s no gzip error).


Michael[tm] Smith https://people.w3.org/mike

Received on Monday, 10 August 2015 03:05:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 14:18:13 UTC