Re: URL not following some 302 redirects after recent changes

[Diane Murray]

On Wed, 22 Nov 2006 03:35:17 +0100 I wrote:
> Sometime after 2006-10-26 URL redirects stopped working correctly
> (Emacs CVS of 2006-09-19 and 2006-10-26 works, 2006-10-31 and
> 2006-11-19 don't work), perhaps due to changes made in revision 1.36
> of url-http.el.

It seems that every time the redirects aren't working is when servers
using HTTP/1.0 send a "Connection: close" header in their 302 response
- 302 responses from servers using HTTP/1.1 work, even when they send
"Connection: close".  Some sites where URL does not redirect correctly
are <http://www.cliki.net> (as mentioned in my original email),
<http://livejournal.com>, and <http://fsf.org>.  Here's an example
with fsf.org.

URL requests:

  GET / HTTP/1.1 
  MIME-Version: 1.0 
  Connection: keep-alive 
  Extension: Security/Digest Security/SSL 
  Host: fsf.org 

The server at fsf.org, using HTTP/1.0, returns the following.  The
connection status for the process changes from "open" to "connection
broken by remote peer ", so `url-http-async-sentinel' activates the
callback.

  HTTP/1.0 302 Moved Temporarily
  Date: Sat, 27 Jan 2007 17:20:20 GMT
  Server: Apache/1.3.33 (Debian GNU/Linux) mod_python/2.7.10 Python/2.3.5 
PHP/4.4.0-3 mod_ssl/2.8.24 OpenSSL/0.9.7g
  Location: http://www.fsf.org/
  Content-Type: text/html; charset=iso-8859-1
  X-Cache: MISS from www.fsf.org
  X-Cache-Lookup: MISS from www.fsf.org:80
  Connection: close
  ...