-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Adrian,
On 2/17/2011 10:51 AM, Adrian Fretwell wrote: > Thank you for your feedback, I have just confirmed CRLF is actually > present by using http://www.askapache.com/online-tools/http-headers-tool/ > When I grab the headers myself in a hex dump, only LF is present. > Something must be stripping the CR out. If your (or some library) code is using Reader.readline then it will remove environment-specific newline characters (that would be CR on older Mac OS, CRLF on DOS-based OSs including Microsoft Windows, and LF on *NIX environments). Unless you're running Mac OS 9 or something, I would be surprised if this is the cause. It's a little unclear from your statement above: where can you observe the correct CRLF separators and where can you observe the absence of the CR characters? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1kEBoACgkQ9CaO5/Lv0PDc8gCgi/n+oVrvppujWSQ26oS0V7nz bW4An1W60GanktsowfLOHlyJfDjZqESl =TiFM -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
