On Mon, 6 Jun 2005 Ken.Thomson@xxxxxxxxxxxxxxxx wrote:
You are right; the error is because there is no blank line delineating
the response headers from the response body. What STABLE release
started to enforce this? It must be between STABLE6 and STABLE10.
http://www.squid-cache.org/Advisories/SQUID-2005_5.txt
Just curious - does the case of response headers matter at all?
It was hard to tell reading the RFCs if the case of the header name was
important.
RFC 2616 4.2 Message Headers
HTTP header fields, which include general-header (section 4.5),
request-header (section 5.3), response-header (section 6.2), and
entity-header (section 7.1) fields, follow the same generic format as
that given in Section 3.1 of RFC 822 [9]. Each header field consists
of a name followed by a colon (":") and the field value. Field names
are case-insensitive. The field value MAY be preceded by any amount
of LWS, though a single SP is preferred. Header fields can be
extended over multiple lines by preceding each extra line with at
least one SP or HT. Applications ought to follow "common form", where
one is known or indicated, when generating HTTP constructs, since
there might exist some implementations that fail to accept anything
beyond the common forms.
Regards
Henrik
