You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a client sends a CONNECT to HTTP::Proxy that includes a Content-
Length header then the result is a hang of the proxy.
It's obviously not a normal condition, but it happened on my
configuration using PHP with cURL and the Google Api library. This
library explicitly sets a Content-Length header for a POST request and
cURL sends it in the CONNECT request to the proxy. I think it's a cURL
wrong behavior, but it was much more easier to fix on the proxy side.
The solution was simply to add this line:
$len = $ct = $te = undef if $method eq "CONNECT";
after this code:
my $te = $r->header('Transfer-Encoding');
my $ct = $r->header('Content-Type');
my $len = $r->header('Content-Length');
This way wrong headers are pretty ignored.
I don't know if anyone else will ever have the same problem, I think
it's not a common situation, anyway I like to report it.
The text was updated successfully, but these errors were encountered:
Migrated from rt.cpan.org#76988 (status was 'new')
Requestors:
From vbuttazzo@yahoo.com on 2012-05-04 13:45:17
:
The text was updated successfully, but these errors were encountered: