[Livehttpheaders] bug on mac? cut and paste double spaces.
Mark Harrison
mh at pixar.com
Mon Mar 10 11:47:54 PDT 2008
Nikolas Coukouma wrote:
> This is due to HTTP's use of "\r\n" for newlines; *nix based systems
> (including OS X) either display "\r" 'oddly' (e.g. ^M) or count both as
> newline characters (as if it were "\n\n").
Ah, got it. It seems most of my applications are treating it
as "\n\n". Perhaps in the future there could be an option
to trim the "\r" when the headers are copied.
Thanks!
Mark
More information about the Livehttpheaders
mailing list