So .. my company makes a portal for network management apps. One of the vendors we support has a product which implements a broken webserver .. it stuffs an extra CRLF after the header (so instead of 2, there's 3). THis is clearly in violation of HTTP1.1, but getting the vendor to fix his product is virtually impossible.
While analyzing the problem, it occurs to us that it might be sensible, in the case of a non-persistent connection (and with "strict" turned off) to arrange httpclient to read to end-of-stream instead of content-length (which would fix our problem in a less hacky way then the other alternatives). If this doesn't cause too much heartache for the dev team I'd be happy to submit a patch .. if someone has a real issue I'd like to hear why. thanks john d'Ausilio edge technologies, inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
