>captured headers contain CR/LF on Linux, should be just newlines

Why should it just be newlines? You're working with a protocol, not a text file.

RFC 2616:
   HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all
   protocol elements except the entity-body (see appendix 19.3 for
   tolerant applications).

If anything, curl should strip the newlines entirely off of recieved headers, not converting them to some platform specific concepts.

---
** [bugs:#1242] captured headers contain CR/LF on Linux**
**Status:** open
**Created:** Thu Jun 06, 2013 06:59 PM UTC by David Biesack
**Last Updated:** Thu Jun 06, 2013 06:59 PM UTC
**Owner:** nobody
captured headers contain CR/LF on Linux, should be just newlines:
    $ curl --version
    curl 7.21.6 (x86_64-pc-linux-gnu) libcurl/7.21.6 OpenSSL/1.0.0e zlib/1.2.3.4 libidn/1.22 librtmp/2.3
    Protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 po
    $ curl --dump-header /tmp/h.txt https://sourceforge.net/p/curl/bugs/new/ > /dev/null
    $ od -c /tmp/h.txt | tail -2
    0000360   t   h   :       2   6   1  \r  \n  \r  \n
    0000373
I realize this could be a breaking change for those who now expect this,
but it is uneexpected; an option could be added for backward compatibility.
---
Sent from sourceforge.net because you indicated interest in <https://sourceforge.net/p/curl/bugs/1242/>
To unsubscribe from further messages, please visit <https://sourceforge.net/auth/subscriptions/>