🚀 go-pugleaf

In article <122u7b.e07.ln@jarl.webthing.com>, Nick Kew
<nick@fenris.webthing.com> writes

>It's the HTTP status line and headers that are malformed.
>An HTTP response is required to take (with example values) the form:
>
>HTTP/1.0 200 OK\r\n
>Server: good-server\r\n
>Date: Sun Apr 20 12:30:16 BST 2003\r\n
>Connection: close\r\n
>Content-Type: text/html;charset=latin1\r\n
>Content-length: 1234\r\n
>\r\n
>[ HTML document here; this is just misc bytes as far as HTTP is concerned ]
>
>Demon is instead serving:
>
>HTTP/1.0 200 OK\n
>Server: broken-server\n
>Date: Sun Apr 20 12:30:16 BST 2003\n
>Connection: close\n
>Content-Type: text/html;charset=latin1\n
>Content-length: 1234\n
>\n
>[ HTML document here; this is just misc bytes as far as HTTP is concerned ]
>
>
>This is malformed, and requires error correction to work.

see RFC 2616, Appendix 19.3

   The line terminator for message-header fields is the sequence CRLF.
   However, we recommend that applications, when parsing such headers,
   recognize a single LF as a line terminator and ignore the leading CR.

ie: the dropping of the CR is not strictly valid (ie: CR and LF should
be sent in the header section). However this should NOT be causing a
problem to anyone who kept reading all the way to the end of the RFC !

As to the "BST" issue... I cannot get the Demon Homepages server to
produce anything other than GMT times.

-- 
richard                       writing to inform and not as company policy

"Assembly of Japanese bicycle require great peace of mind" quoted in ZAMM