IIS 6 HTTP GET Request Fails if headers have LF instead of..

I have the following problem:

I submit GET requests to an IIS 6 server. I have specific headers that
are separated by linefeeds (char 10, \r). Under IIS 5, these requests
are processed fine. But under IIS6, it is ignoring these headers. To
get things to work I have to use carriage return and a linefeed (char
13 + char 10, \r\n).

Can anyone tell me why this has changed under IIS6?

Can anyone tell me if it is possible to configure this behaviour under
IIS 6 and how to change it back to accepting purely a \n character
between hearders?

It should be noted that it is not a viable option for me to change the
code that generates the headers.

Any help would be appreciated!

thanks, Andrew

IIS is finally adhering to standards. HTTP uses CRLF pairs to separate
lines, requests that use LF only are not valid HTTP requests and as such
should be ignored (well, IIS should reply with 400).

Jerry

"Andrew" <theshadow330 RemoveThis @hotmail.com> wrote in message
news:d7085cb6.0308270358.4adfc942@posting.google.com...
 > I have the following problem:
 >
 > I submit GET requests to an IIS 6 server. I have specific headers that
 > are separated by linefeeds (char 10, \r). Under IIS 5, these requests
 > are processed fine. But under IIS6, it is ignoring these headers. To
 > get things to work I have to use carriage return and a linefeed (char
 > 13 + char 10, \r\n).
 >
 > Can anyone tell me why this has changed under IIS6?
 >
 > Can anyone tell me if it is possible to configure this behaviour under
 > IIS 6 and how to change it back to accepting purely a \n character
 > between hearders?
 >
 > It should be noted that it is not a viable option for me to change the
 > code that generates the headers.
 >
 > Any help would be appreciated!
 >
 > thanks, Andrew<!-- ~MESSAGE_AFTER~ -->