Daniel Stenberg wrote:
> > - Either a Content-Range header field (section 14.16) indicating
> > the range included with this response, or a multipart/byteranges
> > Content-Type including Content-Range fields for each part. If a
> > Content-Length header field is present in the response, its
> > value MUST match the actual number of OCTETs transmitted in the
> > message-body.
>
> Since there was a Content-Length header field present in the response, and
> the value was zero, the server did not work as this describes.

This header is in the response:

   Via: 1.1 netcache02 (NetCache NetApp/5.5R4)

Maybe the server is not standard-conforming ... but maybe it's the proxy?
Try the request again, but bypassing the proxy?

Even if the origin server is broken, the proxy should not be able to produce
this kind of response with a non-empty message-body.

-- Jamie
Received on 2005-03-16