Re: [squid-users] persistent HTTP broken in 202 Accepted

On Thu, 15 Sep 2005, Miguel A Paraz wrote:

> It's simply the following. No headers. What is the proper response -
> should there be a content length?
>
> Connected to x.x.x.x
> Escape character is '^]'.
> POST / HTTP/1.0
> Content-Length: 0
>
> HTTP/1.1 202 Accepted
>

The following is what is expected:

POST / HTTP/1.0
Content-Length: 0
Connection: keep-alive

HTTP/1.1 202 Accepted
Server: Description of server
Content-Type: text/html
Content-Length: <somenumber>
Connection: keep-alive
[maybe additional headers, not relevant to the question]

Some HTML text describing the action taken by the server, exacly
"Content-Length" octets long.

If Content-Length or Connection is not correct the connection can not be
kept persistent. Content-Length may be 0 if there is no message
describing the action taken but the specifications mandates there SHOULD
be a message..

RFC 2616 4.4 Message Length

RFC 2616 10.2.3 202 Accepted

Regards
Henrik
Received on Thu Sep 15 2005 - 04:45:51 MDT