On 03/08/2004, at 7:40 AM, Dan Wilga wrote:
At 12:02 PM -0700 8/2/04, Stas Bekman wrote:Upon sending the response. The original error message happens in my code when I try to "print" the HTTP header.
Yeah, that's what I thought. I suppose we could handle that internally then. But I want to have a failing test first. It should work with LWP, just as you see in LWP. Not sure how to arrange that with LWP. Ideas? We need to start the request and then kill it. I suppose we could do an alarm handler, but with 5.8.0 safe signals things, I'm not sure it will actually work. Can you give it a try?
I'm using LWP::UserAgent::timeout (which essentially uses alarm), and am not having any luck reproducing the problem yet. The timeout does happen, but apparently LWP drops the connection in a different way from IE, because the error doesn't occur. I'm even using SSL to test this.
I seem to recall a known IE bug with the way it drops connections when using
SSL. Maybe google for "ssl-unclean-shutdown" together with "MSIE"? I think it
also suffers when keepalive is used, in that sometimes it will send incorrect
content-length headers with POST requests.
Cheers,
Nick -- Nick Phillips / +64 3 479 4195 / [EMAIL PROTECTED] # these statements are my own, not those of the University of Otago
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
