Questions[querystring](server)

Is it possible to use URL Rewrite to provide more complex query string functionality than the "Append query string" checkbox that it has? Specifically, is it possible to specify the keys for certain query string parameters and have it only append those name value pairs.

For example, for the input:

http://www.example.org/test?alpha=1&beta=2&gamma=3

and the list of query string parameter keys: beta gamma

it should output: http://www.example.org/redirect?beta=2&gamma=3

(Note that the query string parameters in the input appear in arbitrary order.)

We've encountered a strange issue (a bug, perhaps?) with Apache mod_rewrite's behavior when passing through query strings.

To reproduce, we've set up a clean Ubuntu (oneiric) install with the default Apache configuration. We have enabled mod_rewrite, and in the default site configuration, we've added the following:

RewriteEngine on
RewriteRule ^/(.*)$ /r/$1 [R]

To test, we use curl:

curl -I 'http://[ubuntu-machine]/a/b%20c?a%20b'

The relevant output is:

HTTP/1.1 302 Found
Server: Apache/2.2.20 (Ubuntu)
Location: http://[ubuntu-machine]/r/a/b%20c?a%2520b

As you can see, the query string is double-escaped, which is wrong. Does anyone have any idea how we could fix this? A couple of things we've tried:

• Adding [NE]. This gives us the correct query string, but the path is unescaped, which leads to new problems.
• Adding [NE,B]. This seems to work, but causes the / between the a and b parts of the path to be escaped.

• Unescaping the query string manually.

  RewriteCond %{QUERY_STRING} .*
  RewriteMap unescape int:unescape  
  RewriteRule ^(.*)$          $1?${unescape:%{QUERY_STRING}}
  

  However, this means we cannot distinguish between, say, an & and an escaped & in the query-string.

Update:

This bug report describes the same issue. The first comment links to a commit apparently fixing the issue, but as Pieter says below, it doesn't seem like it is actually fixed.

This htaccess snippet is supposed to redirect

myhost.com/?p=1&preview=true

to

alt.myhost.com/?p=1&preview=true

RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} ^myhost.com$ [NC]
RewriteRule ^/\?p=([0-9]+)&preview=true$ http://alt.myhost.com/?p=$1&preview=true [NC,R=301,L]

but for some reason I can't escape the / and ? part of the URL. Not sure why this isnt working...

I've tried escaping ?

\\? \? [?]

and I've tried escaping the /

\\/ \/ [/]

none of these seem to work either...

help!

Is there any way to parse HTTP request data in wireshark? For example, can I expose the request parameters upon an HTTP GET request (being sent by my machine), so that I don't need to read the (sometimes) truncated URL and find them by myself?

I was using Tamper Data and Firebug, on my Firefox, to analyse these requests, but they're not as reliable as a stand-alone tool for monitoring my network interface, but wireshark keeps data too raw concerning HTTP flow.

If you guys know any other stand-alone tool that does this (must be Linux-compatible), please tell me.

Thanks!

I'm using mod_rewrite to rewrite URLs like this:

http://example.com/1,2,3,4/foo/

By doing this in .htaccess:

RewriteEngine On
RewriteRule ^([\d,]+)/foo/$ /foo.php?id=$1 [L,QSA]

It works fine, except for when "1,2,3,4" turns into a string longer than 255 characters, Apache returns a "403 Forbidden".

There is no problem visiting foo.php?id=1,2,3,4 directly, even with a very long id string, however this isn't an option for me.

Is there some Apache or other setting I should tweak?

UPDATE: I turned RewriteLog on with RewriteLogLevel 9. With a short id string, I get several lines in my log file. But when the id string is greater than 255 chars., nothing is logged (seems as though mod_rewrite isn't even executing?).

If you find this question interesting/helpful, please upvote it.