Hello >> Then you did not reproduce my test conditions. Please try a CRLF >> message with lineStripping disabled. Do you get garbage? > > This is reproducable with git master/HEAD. I actually noticed this > behaviour already last week while working on something else, but did > not > have time yet to look further into it.
Thanks. >> If yes, please try my patch, still with lineStripping disabled. > > The nominal case is that incoming data has CRLF linefeeds, thus the > empty line between headers and body contains CRLF. In decode.c, this > means that this line contains CR. > > While processing the nominal input (CRLF) and not in daemon mode, > this > only works with Broken Linestripping enabled, which is not the > default. > Your patch fixes this, so I can only agree. Could you please take a little more time and tell me what you think about this: I have the feeling the lineStripping option could be completely removed, along with its code. I am asking because I don't really see a use case that would not already be covered by the code. Thanks -- Sylvain ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
