[wp-meta] [Making WordPress.org] #210: Infinite redirect loop for non-ASCII URLs

Making WordPress.org noreply at wordpress.org
Fri Oct 18 08:29:56 UTC 2013

#210: Infinite redirect loop for non-ASCII URLs
Reporter:  toscho  |      Owner:
    Type:  defect  |     Status:  new
Priority:  normal  |  Component:  Support Forums
Keywords:          |
 When I try to open this URL …


 GET /support/topic/hasn%E2%80%99t-this-become-obsolete?replies=1 HTTP/1.1
 User-Agent: Opera/9.80 (Windows NT 6.1; Win64; x64) Presto/2.12.388
 Host: wordpress.org
 Accept: text/html, application/xml;q=0.9, application/xhtml+xml,
 image/png, image/webp, image/jpeg, image/gif, image/x-xbitmap, */*;q=0.1
 Accept-Language: en,de;q=0.9
 Accept-Encoding: gzip, deflate
 Cookie: /* removed */
 Cookie2: $Version=1
 Cache-Control: no-cache
 Connection: Keep-Alive
 DNT: 1

 … I get in Opera 12 a useless response, sending me to the same address
 with non-ASCII characters encoded in lowercase:

 HTTP/1.1 302 Found
 Server: nginx
 Date: Fri, 18 Oct 2013 08:23:07 GMT
 Content-Type: text/html; charset=UTF-8
 Connection: close
 Expires: Wed, 11 Jan 1984 05:00:00 GMT
 Last-Modified: Fri, 18 Oct 2013 08:23:07 GMT
 Cache-Control: no-cache, must-revalidate, max-age=0
 Pragma: no-cache
 Location: http://wordpress.org/support/topic/hasn%e2%80%99t-this-become-
 X-nc: BYPASS lax 250

 This continues until my browser has enough.

 In Chrome, I don’t get a 302, the correct page is sent instead.

 Looks like broken UA sniffing.

Ticket URL: <http://meta.trac.wordpress.org/ticket/210>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software

More information about the wp-meta mailing list