On May 5, 2005, at 16:23, Tim Cheadle wrote:
On Thu, 2005-05-05 at 10:48 -0400, Tim Cheadle wrote:
Any reason not to do this for other methods as well?
Because the other methods in HTTP 1.0 (GET and HEAD) don't
require it,
nor does it make sense as they don't have any post-header content to
send.
Right, but there's methods in 1.1 (for which Client::HTTP is being
rewritten) that can have content (e.g. PROPFIND). So why not just add
a content-length header whenever there is content?
Per the PoCo::Client::HTTP perldoc:
BUGS
HTTP/1.1 requests are not supported.
This bug has been fixed. Unfortunately it invalidates your patch. I
would still like the component to do the right thing, but I don't
know enough about the various HTTP protocol versions to say what that
might be.
If you'd like to resubmit your patch for POE::Component::Client::HTTP
at its current revision, I would be happy to apply it.
--
Rocco Caputo - http://poe.perl.org/
