> Sure, here, fixing that is a no brainer (it also will save a few bytes in
> the request). However, in more complex cases, it's definitely conformance to
> the standard which matters.
>
> If anyone could send a pointer to the chapter in the HTTP/1.1 spec which
> says that Content-Length: 0 is not allowed in a GET method, I would be
> interested.
>
I had a quick look - there's nothing that says it isn't allowed. There's
one paragraph which weakly implies that it isn't allowed, but there are
other paragraphs that specifically state that a content-length of 0 IS
allowed. So I think that the client code is doing the right thing, in so
far as it isn't doing anything that ISN'T allowed, but it does seem to
cause problems with certain other programs.
If you don't think this should be changed in slide (which is fair
enough), that's fine with me - my proxy support is an ugly hack anyway,
another ugly hack isn't a problem :)
Hopefully I'll have time at some point (probably not soon, though) to
clean up the proxy stuff so that it's a neat addition rather than the
current hack, and then maybe we can return to this problem.
Michael
