[RESOLVED] mod_rewrite problem

Scripteen

I'm using mod_rewrite to make some nice urls but I have a problem with this line

RewriteRule files/(.*) files.php?hash=$1

Now if the file hash has / in it, the link breaks

How to solve this?

bpat1434

What do you mean it breaks? It works perfectly fine in my tests.

RewriteEngine On
RewriteRule files/(.*) files.php?hash=$1

Scripteen

bpat1434;10927025 wrote:
What do you mean it breaks? It works perfectly fine in my tests.
RewriteEngine On
RewriteRule files/(.*) files.php?hash=$1

this is a sample url

http://www.site.com/files/wUtGI1y6/2FgI

it gives 404 page

but http://www.site.com/files.php?hash=wUtGI1y6/2FgI

works fine

bpat1434

Still works as expected when I test it....

dagon

any other rewrite rules in effect ?

Scripteen

bpat1434;10927069 wrote:
Still works as expected when I test it....

Take this link for example

http://www.zoxel.com/game/264/

/game/264/ rewrites to file.php?id=264

now if the url is

http://www.zoxel.com/game/264/11

You get 404 page because the number 11 after the second / is considered as another parameter.

What I'm asking for is a rule that considers everything after the first slash as a single parameter.

PS: I don't control the file hash so I can't generate one that has no / in it.

dagon;10927070 wrote:
any other rewrite rules in effect ?

Just another typical rule that rewrites to another file.

bradgrafelman

Scripteen wrote:
You get 404 page because the number 11 after the second / is considered as another parameter.

No, you are getting a 404 page for some reason; it's working fine for the rest of us. There are no "parameters" in the URL at this point - it's just a string of characters you're examining in mod_rewrite.

The code you posted worked fine for me on my local installation of Apache 2.2 (and yes, I did try URLs such as /files/test/me and they worked fine).

Scripteen

bradgrafelman;10927075 wrote:
No, you are getting a 404 page for some reason; it's working fine for the rest of us. There are no "parameters" in the URL at this point - it's just a string of characters you're examining in mod_rewrite.

The code you posted worked fine for me on my local installation of Apache 2.2 (and yes, I did try URLs such as /files/test/me and they worked fine).

I'm using apache 2.2 as well. What makes me know that it is rewrite problem is that when I use file.php?hash=1111/1111 it works fine without any problem so it is just the rewrite rule.

Also note that it is a 404 error not a php error so the error is not coming from the php code rather than a broken link caused by mod_rewrite

Can you please post code for your test php file and .htaccess file?

Thanks

bpat1434

Scripteen, I've posted the EXACT code I have in my .htaccess code for you that is working exactly how you want it to work.

Perhaps you should show us your entire .htaccess file? I'm willing to be there's something in there that's messing it up.

Test it yourself here:
Click here

Scripteen

bpat1434;10927096 wrote:
Scripteen, I've posted the EXACT code I have in my .htaccess code for you that is working exactly how you want it to work.

Perhaps you should show us your entire .htaccess file? I'm willing to be there's something in there that's messing it up.

Test it yourself here:
Click here

I figured out the problem, the hash passes to the .htaccess file encoded

wUtGI1y6%2FgI%3D

which is

wUtGI1y6/gI=

I applied urldecode on the hash before passing it to the htaccess file and it works fine now. Thanks all for your help 🙂

bpat1434

Glad we could be of assistance.