go to bug id or search bugs for
Any HTTP request in http://pear.php.net/get/ take a long
time (about 2 minutes) to process. Any other page on the
site works fine.
The client will send a HTTP GET request to a URL in http://
pear.php.net/get/. Many seconds later the server will
respond with the response and payload. Some browsers time
out because the requests takes so long. The pear command
doesn't even work because of the delay.
This problem only occurs from some addresses. The problem
also occurs with other sites running similar mirror
resolution scripts (like www.php.net and www.mysql.com). In
my case, the problem exists for my entire university
network. The network engineers suspect it has something to
do with our ISP, but we don't know what. We are not sure if
the problem is with the server-side script or somewhere on
our end, including our ISP.
Only possible from some addresses. I can provide a shell account to a machine where the problem exists. Any address in 22.214.171.124/255.255.0.0 is affected.
Download requests are responsive.
Download requests are painfully slow.
Add a Patch
Add a Pull Request
Considering that only certain subnets are affected, this is most likely a firewall/routing/QoS issue on your side.
Just to make it clear: Neither are we running any mirror redirection similar the systems used by MySQL or PHP nor are we employing a throttling infrastructure for the downloads.
Thank you for the prompt reply.
I am inclined to believe that there is some script voodoo/
transparent redirect happening at http://pear.php.net/get/
just because of the URL layout. Is there any chance I could
get a direct IP address or URL to download a file so I may
go to our ISP with something concrete. If the direct
download went as normal, then I could definitely say that
the problem is on my end.
If I am wrong about requests in /get/, just say so and we
will consider this bug closed.
/get is a simple PHP script. It only lacks the .php extension. Unfortunately there is no other way to download files.
If you could tell me the IP address of your requests, I can query the access logs to see if anything magic goes on.
I have made requests from 126.96.36.199 today with multiple