Re: [bug-cgicc] No carriage returns?

[Stephen F. Booth]

Hi Walter,

It's been forever since I've looked at the cgicc code but it does seem this non-compliant behavior goes back to at least 2001.  RFC 2616 supersedes RFC 2068 but both require CRLF as the end of line separator.  However, RFC 2068 has the following note in 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.

which explains why this bug doesn't seem to affect most browsers.  It should still be fixed, however.

Stephen

On Tue, Jan 28, 2014 at 5:16 PM, Walter Landry <address@hidden> wrote:

Hello,

I was trying out cgicc, and I noticed that cgicc does not insert the
required carriage returns "\r".  For example, in

  http://www.gnu.org/software/cgicc/doc/cgicc_tutorial.html

the section "The HTTP Response" states

  A standard HTML 4.0 document need only output a single header:

    cout << cgicc::HTTPHTMLHeader() << endl;

  This will generate the output

    Content-Type: text/html\n\n

I thought that RFC 2068 mandates

    Content-Type: text/html\r\n

Am I missing something?

Thanks,
Walter Landry
address@hidden

_______________________________________________
bug-cgicc mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/bug-cgicc