Re: other proxies

From: Graham Leggett <minfrin(at)sharp.fm>
Date: Tue Apr 24 2001 - 17:24:31 EDT

Chuck Murcko wrote:

> It looks like we may not like talking to akamai very well.

Something really nasty is happening here.

Requests from akamai servers are arriving fine from the remote server, but while the proxy is shipping the data back to the browser the proxy suddenly freezes.

Over time, as all the available threads hang and run out, Apache suddenly starts creating children which segfault immediately on startup, generating a very large logfile very quickly full of dying children.

I've tried to figure out what is special about akamia requests - notably they seem to be aimed at servers that claim to be HTTP/1.0.

Here is a request from the proxy to akamai:

GET /7/772/51/e964b28d59e412/www.apple.com/   home/images/03/macosx_nowshipping.gif HTTP/1.1 Host: a772.g.akamai.net
Accept: image/gif, image/x-xbitmap, image/jpeg,   image/pjpeg, image/png, */*

Accept-Charset: iso-8859-1,*,utf-8
Accept-Encoding: gzip
Accept-Language: en

Pragma: no-cache
User-Agent: Mozilla/4.7 [en] (X11; I; Linux 2.2.18 ppc) Max-Forwards: 10
Via: 1.0 127.0.0.1 (Apache/2.0.18-dev)

And the response from akamai goes like this:

HTTP/1.0 200 OK
Server: Apache/1.3.9 (Mac OS X Server)
Last-Modified: Sat, 24 Mar 2001 02:57:28 GMT ETag: "2474ca-2365-3abc0d18"
Accept-Ranges: bytes
Content-Length: 9061
Content-Type: image/gif
Date: Tue, 24 Apr 2001 20:58:26 GMT
Connection: keep-alive

The full response is returned (all 9061 bytes of it) correctly.

The URL is very long - but I tested it locally with a hugely long URL and it worked...

The next thing to investigate is mod_proxy's behavior against HTTP/1.0 servers.

Regards,
Graham

-- 
-----------------------------------------
minfrin@sharp.fm		"There's a moon
					over Bourbon Street
						tonight..."

Received on Tue Apr 24 21:39:55 2001