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 also tried setting the user agent string of the request to match what IE sends, and this made no difference. I'm beginning to wonder if maybe I need to sniff the packets.
Are you by chance using a proxy server?
Nope. Good thought, though.
-- Dan Wilga [EMAIL PROTECTED] Web Technology Specialist http://www.mtholyoke.edu Mount Holyoke College Tel: 413-538-3027 South Hadley, MA 01075 "Who left the cake out in the rain?"
-- 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