Re: Improve can't gunzip content error

--047d7bb04272c53117051cecfc29
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Mike,

Thanks for confirming. I will use the Nu validator going forward.

Thanks,
Joe

On Sun, Aug 9, 2015 at 9:04 PM, Michael[tm] Smith <[email protected]> wrote:

> Hi Joe,
>
> Joe Merrill <[email protected]>, 2015-08-06 10:08 -0600:
> > Archived-At: <
> http://www.w3.org/mid/CAHeScEg3CXuxRCwr5=3DaOEPNKba6ivs4WxZgD70VRPPiBp9XU=
[email protected]
> >
> >
> > 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,
> https://validator.w3.org/)
>
> 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=3Dhttp://www.mdsupplies.com works a=
s
> expected, and that=E2=80=99s 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 respon=
se
> > 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=E2=80=99s no gzip err=
or).
>
>   =E2=80=94Mike
>
> --
> Michael[tm] Smith https://people.w3.org/mike
>

--047d7bb04272c53117051cecfc29
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Mike,<div><br></div><div>Thanks for confirming. I will =
use the Nu validator going forward.</div><div><br></div><div>Thanks,</div><=
div>Joe</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Sun, Aug 9, 2015 at 9:04 PM, Michael[tm] Smith <span dir=3D"ltr">&lt;<=
a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Hi Joe,<br>
<br>
Joe Merrill &lt;<a href=3D"mailto:[email protected]">jmerrill@c=
rankingsoftware.com</a>&gt;, 2015-08-06 10:08 -0600:<br>
&gt; Archived-At: &lt;<a href=3D"http://www.w3.org/mid/CAHeScEg3CXuxRCwr5=
[email protected]" rel=3D"noreferrer" targ=
et=3D"_blank">http://www.w3.org/mid/CAHeScEg3CXuxRCwr5=3DaOEPNKba6ivs4WxZgD=
[email protected]</a>&gt;<br>
<span class=3D"">&gt;<br>
&gt; While trying to validate <a href=3D"http://www.mdsupplies.com" rel=3D"=
noreferrer" target=3D"_blank">http://www.mdsupplies.com</a> the following e=
rror is<br>
&gt; show:<br>
&gt;<br>
&gt; A fatal error occurred when attempting to decode response body from<br=
>
&gt; <a href=3D"http://www.mdsupplies.com/" rel=3D"noreferrer" target=3D"_b=
lank">http://www.mdsupplies.com/</a>. Either we do not support the content =
encoding<br>
&gt; specified (&quot;gzip&quot;), or an error occurred while decoding it.<=
br>
&gt;<br>
&gt; The error was: Can&#39;t gunzip content: Header Error: Minimum header =
size is<br>
&gt; 10 bytes<br>
<br>
</span>Yeah, that seems to be a bug in the legacy Markup Validator (that is=
,<br>
<a href=3D"https://validator.w3.org/" rel=3D"noreferrer" target=3D"_blank">=
https://validator.w3.org/</a>)<br>
<br>
I have no idea how to troubleshoot it. But the fix is just to not use the<b=
r>
legacy Markup Validator but instead to just use the current W3C HTML<br>
Checker (<a href=3D"https://validator.w3.org/nu/" rel=3D"noreferrer" target=
=3D"_blank">https://validator.w3.org/nu/</a>).<br>
<span class=3D""><br>
&gt; The same page can be validated by the Nu validator with no errors.<br>
<br>
</span>Yeah <a href=3D"https://validator.w3.org/nu/?doc=3Dhttp://www.mdsupp=
lies.com" rel=3D"noreferrer" target=3D"_blank">https://validator.w3.org/nu/=
?doc=3Dhttp://www.mdsupplies.com</a> works as<br>
expected, and that=E2=80=99s the recommended tool to use.<br>
<span class=3D""><br>
&gt; It can also be fetched by google and displays correctly in all browser=
s.<br>
&gt; If this error could show the request/response headers it would be very=
<br>
&gt; useful. Or if it could list the actual specification(s) that the respo=
nse<br>
&gt; is violating.<br>
<br>
</span>There is no problem with the response. You can verify that by doing =
this:<br>
<br>
=C2=A0 curl -s -H &quot;Accept-Encoding: gzip&quot; <a href=3D"http://www.m=
dsupplies.com" rel=3D"noreferrer" target=3D"_blank">http://www.mdsupplies.c=
om</a> | gunzip -t<br>
<br>
Which as expected returns nothing (indicating there=E2=80=99s no gzip error=
).<br>
<br>
=C2=A0 =E2=80=94Mike<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Michael[tm] Smith <a href=3D"https://people.w3.org/mike" rel=3D"noreferrer"=
 target=3D"_blank">https://people.w3.org/mike</a><br>
</font></span></blockquote></div><br></div>

--047d7bb04272c53117051cecfc29--