Hi Edd, I've been working on this some more and have formed my latest theory as to what's gone wrong. I think both the Apache distribution and this one are breaking the HTTP 1.1 spec in RFC2616:
You: - Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding. and - The Content-Length header field MUST NOT be sent if these two lengths are different (i.e., if a Transfer-Encoding header field is present). Us: - If the message does include a non-identity transfer-coding, the Content-Length MUST be ignored. and - If a message is received with both a Transfer-Encoding header field and a Content-Length header field, the latter MUST be ignored. -- Ryan Hoegg ISIS Networks Edd Dumbill wrote: >OK, I figured this out. Your request header has HTTP/1.1 in it. If >that's what you send, that's what the web server expects you to speak! > >The ones your program worked against worked because they don't implement >HTTP/1.1. > >Change your request to HTTP/1.0, or implement HTTP/1.1 properly :) > >-- Edd > >
