[wp-trac] [WordPress Trac] #5089: Canonical Redirect causes continual 301 redirect loop

[WordPress Trac]

#5089: Canonical Redirect causes continual 301 redirect loop
--------------------------+-------------------------------------------------
 Reporter:  wcraigtrader  |       Owner:  anonymous
     Type:  defect        |      Status:  new      
 Priority:  normal        |   Milestone:           
Component:  General       |     Version:  2.3      
 Severity:  critical      |    Keywords:  redirect 
--------------------------+-------------------------------------------------
 I have a somewhat convoluted setup that works fine with WordPress 2.2, but
 is broken horribly by WordPress 2.3's Canonical Redirect feature.

 I have two webservers:  an external Apache instance that serves multiple
 domains, but for most domains it's really a reverse proxy to an internal
 webserver.  The internal webserver hosts multiple sites, and in
 particular, several WordPress instances.  The internal sites don't have
 anything fancy in their .htaccess files; the external webserver ensures
 that requests to non-canonical domains are redirected correctly.

 When I upgraded one of my sites (http://ludus.unicornsrest.org/) to
 WordPress 2.3, access to the front page (but not the admin pages) was
 broken: it gets a continual 301 redirect to
 http://ludus.unicornsrest.org/.  Here are the headers from curl:

 {{{
 curl -I -L http://ludus.unicornsrest.org/
 HTTP/1.1 301 Moved Permanently
 Date: Thu, 27 Sep 2007 05:35:54 GMT
 Server: Apache/2.0.59 (CentOS)
 X-Powered-By: PHP/5.1.6
 Set-Cookie: PHPSESSID=9vnpn1t6o7b4kbrsk56fn5tgp1; path=/
 Expires: Thu, 19 Nov 1981 08:52:00 GMT
 Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-
 check=0
 Pragma: no-cache
 X-Pingback: http://ludus.unicornsrest.org/xmlrpc.php
 Location: http://ludus.unicornsrest.org/
 Content-Type: text/html; charset=UTF-8
 Connection: close

 HTTP/1.1 301 Moved Permanently
 Date: Thu, 27 Sep 2007 05:35:55 GMT
 Server: Apache/2.0.59 (CentOS)
 X-Powered-By: PHP/5.1.6
 Set-Cookie: PHPSESSID=j9tl0rjulelhop34ji2ioj9ep5; path=/
 Expires: Thu, 19 Nov 1981 08:52:00 GMT
 Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-
 check=0
 Pragma: no-cache
 X-Pingback: http://ludus.unicornsrest.org/xmlrpc.php
 Location: http://ludus.unicornsrest.org/
 Content-Type: text/html; charset=UTF-8
 Connection: close

 HTTP/1.1 301 Moved Permanently
 Date: Thu, 27 Sep 2007 05:35:55 GMT
 Server: Apache/2.0.59 (CentOS)
 X-Powered-By: PHP/5.1.6
 Set-Cookie: PHPSESSID=5pmfi1go1o18biabb0to7ttro5; path=/
 Expires: Thu, 19 Nov 1981 08:52:00 GMT
 Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-
 check=0
 Pragma: no-cache
 X-Pingback: http://ludus.unicornsrest.org/xmlrpc.php
 Location: http://ludus.unicornsrest.org/
 Content-Type: text/html; charset=UTF-8
 Connection: close
 }}}

 I had to download and activate Mark's [http://txfx.net/files/wordpress
 /disable-canonical-redirects.phps plugin] to disable canonical redirects.

 My WordPress and Blog Addresses are set to
 {{{http://ludus.unicornsrest.org}}}.

 I looked (briefly) at the redirect_canonical function, but there's too
 much going on in there for me to determine what the actual problem is.  I
 looked at #5017, but that ticket doesn't provide any insight into my
 problem.

 Is there any way that one of the WP developers could put together a simple
 page that would dump all of the appropriate variables that
 redirect_canonical depends upon, that I could load into my site to give
 you the data you need to see what's going on?  No offense, but I don't
 give *anyone* access to the internal server.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5089>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software