Infinite Redirection in Bogus Namespace

[miqrogroove]

On my WordPress blog, anyone who hits a path like /&a=a= will get locked into an infinite namespace. :(

On wordpress.com, what I get is, "If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header." :o

Should I attach my resume? ^_

[miqrogroove]

Example Location header output

​http://blogyul.miqrogroove.com/&a=a%3D/
​http://blogyul.miqrogroove.com/&a=a%3D%2F/
​http://blogyul.miqrogroove.com/&a=a%3D%2F%2F/
​http://blogyul.miqrogroove.com/&a=a%3D%2F%2F%2F/

[miqrogroove]

http://blogyul.miqrogroove.com/&a=a=
http://blogyul.miqrogroove.com/&a=a%3D/
http://blogyul.miqrogroove.com/&a=a%3D%2F/
http://blogyul.miqrogroove.com/&a=a%3D%2F%2F/
http://blogyul.miqrogroove.com/&a=a%3D%2F%2F%2F/

[GamerZ]

I can't seem to reproduce this, my site loads fine with the query string

[miqrogroove]

This is interesting. I stubbed in a logging command directly above the line " trailing slashes" in canonical.php.

//debug
error_log('rpath:'.$redirect['path']);

	// trailing slashes

It should write one line to the log for my eyes only. But look at the output for a single hit to /&a=a=

[26-Jan-2009 02:09:33] rpath:/&a=a%3D
[26-Jan-2009 02:09:33] rpath:/&a=a%3D/

[miqrogroove]

Okay, I think that second line is a result of the " protect against chained redirects". Now I just need to figure out why the hell that trailing slash is being urlescaped when the client hits /&a=a%3D/

[miqrogroove]

Curiouser and curiouser... When I stubbed in

//debug
error_log('ruri:'.$_SERVER['REQUEST_URI']);

the output was

[26-Jan-2009 02:26:42] ruri:/&a=a%3D%2F

So who's messing with mah superglobals?

[miqrogroove]

qTranslate appears to be the culprit.

[miqrogroove]

Fixed for qTranslate v2.2.2 and patch available at ​http://plugins.trac.wordpress.org/changeset/89547/qtranslate