Re: parsing bug in HTTP::Message::parse()

2005-09-20 Thread Gisle Aas
This problem was fixed in the libwww-perl CVS repository in February, http://cvs.sourceforge.net/viewcvs.py/libwww-perl/lwp5/lib/HTTP/Message.pm?r1=1.56r2=1.57. Unfortunately I've not found the time to roll another official libwww-perl release since then. BTW, the patch above did find it's way

Re: parsing bug in HTTP::Message::parse()

2005-09-20 Thread Brian Hirt
Gilse, Thanks for the response, I'm happy to hear that it's fixed in cvs. Hopefully a new release will be rolled before the years end. --brian On Sep 20, 2005, at 12:59 PM, Gisle Aas wrote: This problem was fixed in the libwww-perl CVS repository in February,

Re: parsing bug in HTTP::Message::parse()

2005-06-16 Thread Gisle Aas
Brian Hirt [EMAIL PROTECTED] writes: Any news on this? It's a pretty major bug. I don't see anything wrong when running your test program. What version of LWP are you using? Regards, Gisle

Re: parsing bug in HTTP::Message::parse()

2005-06-14 Thread Brian Hirt
Any news on this? It's a pretty major bug. --brian On May 30, 2005, at 5:30 PM, Brian Hirt wrote: I'm following up on a bug I've run into with HTTP::Message.I think my original message might have been lost or sent to the wrong address (i sent it to the contact listed in the module,