> The message "Didn't want any more data" occurs during an HTTP POST
> request when the request body overflows its Content-Length. It can
> also happen in HTTP GET if there's any sort of request body. Why
> would IE be overflowing its own Content-Length header?
I don't know, especially since these are straight GET's, no queries
involved. (BTW, was my httpd code up to snuff??? I winged it pretty
heavily... :-).
> A quick "fix" would be to ignore the Content-Length, but I think
> that's covering some badness in Filter::HTTPD with even more badness.
> I'd rather get rid of the original badness than heap more layers atop
> it.
My quick fix was to patch HTTPD.pm to change the C<die> to a C<warn>, for
now.
> Can you create a hex dump of your raw HTTP request, headers and all?
> Maybe I can glean something from that.
I'd love to. But I'm not shure how in POE??
Using HTTP::Daemon, I get:
GET / HTTP/1.1
Connection: Keep-Alive
Accept: */*
Accept-Encoding: gzip, deflate
Accept-Language: en-us
Authorization: Basic XXXXXXXXX
Host: devel:8889
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
Cookie:
Extras:
Here, Extras represents any data read AFTER creating the request object.
So what could possibly be wrong w/ that???
TIA,
Rob
