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

Re: IO error

From: Michael[tm] Smith <mike@w3.org>
Date: Fri, 26 Jun 2015 12:43:54 +0900
To: Alberto Nannini <consulenza@webrevolver.it>
Cc: www-validator@w3.org
Message-ID: <20150626034354.GT7733@sideshowbarker.net>
Alberto Nannini <consulenza@webrevolver.it>, 2015-06-19 00:43 +0200:
> Archived-At: <http://www.w3.org/mid/5583499E.20002@webrevolver.it>
>    your validator rise up an "IO error" validating my site.
>    Here is my homepage url: [1]http://www.notanumber.it/en/
>    Let me know if there is something wrong.

That server is sending a broken gzip response.

I think the response is either missing the standard/expected 8-byte gzip
trailer, or the gzip trailer is corrupted—maybe because the server is
closing the connection before it’s sent the whole response.

If you have the “curl” command around, you can test the server by doing this:

  curl -s -H “Accept-Encoding: gzip”  http://www.notanumber.it/en/ | gunzip -t

You’ll get back the error message “gzip: stdin: unexpected end of file”.

You won’t see that error message if you try the same thing for a URL from a
server that’s sending a valid gzip response; for example:

  curl -s -H “Accept-Encoding: gzip” https://sideshowbarker.net/ | gunzip -t

The reason this doesn’t cause any problems in Web browsers is that I think
browsers will quietly ignore a corrupted or missing trailer. But other
tools (e.g., the gunzip tool) will not. So the right solution to the
problem would be to try to get that server fixed so that it’s not sending
out a broken gzip response.

In the mean time if you want to run the HTML checker on any URLs from that
server, you’ll need to turn off gzip compression on the server (until you
can get the cause figured out and fixed).


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

Received on Friday, 26 June 2015 03:44:19 UTC

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