On Wed, May 31, 2006 at 12:07:16PM -0400, Adam wrote: > I know that example generates "\n" instead of "\r\n", that's why I said > its wrong. Just because apache will fix your incorrect output, doesn't > mean you should go ahead and write CGIs that way and rely on webservers > to fix it for you. Not all of them will, and there's no benefit from > doing it wrong.
Well, I wouldn't say that I am doing it wrong, maybe you are just a little bit intolerant; <snip> RFC2616, 19.3, Tolerant Applications ... 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. ... </snip> The HTTP header termination is a empty message-header field line. In the real world I don't know a single HTTP server which is that intolerant, including my own webserver. My intention was to give somebody a help and not starting an argue with you. And before you start to offend that <snip> is not a vaild HTML tag, I know that by myself ;) Thread over for me. Regards, Marcus -- Marcus Glocker, [EMAIL PROTECTED], http://www.nazgul.ch -----------------
