httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d...@ast.cam.ac.uk (David Robinson)
Subject Re: apache-0.2...
Date Thu, 23 Mar 1995 15:04:00 GMT
Brian wrote:
>> But this particular patch gets -1 either way:
>>  * the patch introduces a bug: a CGI script that sends a Status: header
>>    ending in CRLF causes httpd to send a status line ending in CRCRLF
>> , and
>
>Hmm?  This seems to work alright for me....

Rob wrote:
>I just tried both types of Status: line terminator..
>
>CRLF  and LF
>
>Both came out as CRLF, since apache reads the status code and
>status message, and saves them for later output, always with CRLF
>
>The patch also ensures that the end of header is marked with CRLF
>
>I can't see how you can get CRCRLF

Strange. I've just confirmed the problem. I started with vanilla Apache 0.2,
and applied patch B39_CRLF.txt.

My CGI script starts with:
#!/bin/sh

echo 'Content-type: text/plain'
echo 'Status: 202 Accepted message\015'
echo 

echo CGI/1.0 test script report:
echo

The first data that the client reads is (from gdb):
$1 = "HTTP/1.0 202 Accepted message\r\r\n\000\000..."

 David.

Mime
View raw message