Bug #3043

Pager + mod_rewrite, recursive urlencode() breaks rewrite handler

Details

Submitted	2004-12-28 12:29 UTC
From	benediktlaube at gmail dot com
Assigned	quipo
Status	Closed
Package	Pager
PHP Version	4.3.10
OS	Linux
Roadmaps	(Not assigned)

Comments

[2004-12-28 12:29 UTC] benediktlaube at gmail dot com

Description:
------------
When mod_rewrite together with Pager, the request argument gets urlencoded by Pager. The mod_rewrite handler needs to urldecode() to be able to parse the request. There needs to be recursive urldecode() for each time a Pager link has been clicked. As the number of urldecodes cannot be guessed, there should be an option for mod_rewrite situations to be used alongside Pager.

[2004-12-28 12:32 UTC] benediktlaube at gmail dot com

A hint how to fix the rewrite handler to deal with the unknown number of urlencodes will suffice.

[2005-01-10 12:41 UTC] benediktlaube at gmail dot com

Hi
I am still experiencing problems. The main Problem is due to the mod_rewrite. I use URLs like

http://www.mysite.com/shop/electronics

upon entering the page that has the Pager() Links, everything is fine. The request is attached to the URL by Pager like this:

http://www.mysite.com/index.php?request=shop/electronics&PageID=3 (or 4,5,6,7,...)

Now, when I click a Pager link to get to another page, there the attached request looks like:

http://www.mysite.com/index.php?request=shop%2Felectronics&PageID=3

So when I click a link now, it obviously will not work as my rewrite handler cannot use %2F but needs the '/' as separator.

I don't understand why it's not urldecoded...pls help!