At Adobe, HTTP redirection is hard

Well this sure explains why Firefox is claiming the redirection will result in an infinite loop…

$ curl -i -s -S <b>http://get.adobe.com/reader/</b>
HTTP/1.1 301 Moved Permanently
Server: Apache/2.0.63 (Unix)
<b>Location: http://get.adobe.com/reader/</b>
Keep-Alive: timeout=5, max=500
Content-Type: text/html; charset=iso-8859-1
Accept-Ranges: bytes
Connection: Keep-Alive
Date: Thu, 09 Sep 2010 04:47:10 GMT
Age: 248
Content-Length: 236

But every so often, you’ll get back something that works…

$ curl -i -s -S <b>http://get.adobe.com/reader/</b>
HTTP/1.1 302 Moved Temporarily
Date: Thu, 09 Sep 2010 04:47:11 GMT
Server: JRun Web Server
Content-Type: text/html; charset=UTF-8
Cache-Control: private, no-store, no-cache
Content-Language: en-US
Content-Language: en-US
<b>Location: /reader/otherversions/</b>
Set-Cookie: SETTINGS.LOCALE=en%5Fus;domain=.adobe.com;expires=Sat, 01-Sep-2040 04:47:11 GMT;path=/cfusion/
Set-Cookie: READER_HTTPREFERER=;domain=.adobe.com;path=/
Content-Length: 0
Connection: close

At Adobe, web services are hard. I wonder if they’ve been replacing their system administrators with monkeys.