Re: Bad header syntax -- is this par for the course?

Jamie Lokier wrote:

>Take a look at the HTTP response below, from a real server.
>The line beginning with "CP" is clearly not valid HTTP/1.0 or HTTP/1.1
>syntax.
>
>Is this sort of thing commonplace?
>  
>
Sort of, many servers are broken and output:
Content-Type: text/html\n\n<resource data>

Instead of the correct one:
Content-Type: text/html\r\n\r\n<resource data>

There are _many_ perl scripts (and other) that do this.
So being strict for CRLF parsing is a bad idea.

Apart from that I dont have to worry about broken http much.
Expire dates seem to have all sorts of funny values, but that
is ok for me, only means that the cache will expire quicker.

/robo

Received on Wednesday, 23 June 2004 14:02:08 UTC