Apache – query string rewrite rule appends condition to URL

apache-2.2mod-rewritequeryregex

In trying to rewrite

site-search.html?searchword=search%20term

advanced-search#q=search%20term

I always end up with advanced-search#q=%3Fsearchword%3search%20term

The %3Fsearchword%3 portion is mysteriously appended to the generated URL right before the search term.

The rule I have in place look as follows:

RewriteCond %{REQUEST_URI}  ^/site-search\.html$
RewriteCond %{QUERY_STRING} ^searchword=(.*)$
RewriteRule ^(.*)$ http://www.example.com/advanced-search#q=%1 [R=301,L,NE]

It is worth mentioning that it makes no difference what I put after "q=".
The same error or a slight variation of to will happen regardless.

Best Answer

RewriteRule's %1 comes from the same RewriteRule's (.*) condition, and you match the query string there together with the URI itself.

Solution 1: Move or copy your pattern in the second RewriteCond into the RewriteRule's condition.

Based on the coments, and an assumption what would you like to reach, somehow like this:

RewriteCond %{HTTP_HOST} ^(www\.)?domain.com$
RewriteCond %{REQUEST_URI}  ^/site-search\.html$
RewriteRule [?&]searchword=([^&]*) http://www.domain.com/advanced-search#q=%1 [R=301,L,NE]

Solution 2: explore RewriteRule's the [QSA] flag, which appends the entire query string to the resulting uri for you. (not for Apache 2.2)

Related Solutions

Tomcat – Apache2 – mod_expire and mod_rewrite not working in httpd.conf – serving content from tomcat

Probably the ProxyPass / directive you have in your config routes all requests to the Tomcat backend, bypassing all your mod_rewrite directives. You can try to remove the ProxyPass directive and use RewriteRule with the [P] flag after your other rewrites:

mod_rewrite: P|proxy

For the expire headers the situation is worse — in another similar question a solution was not found.

Option +FollowSymLinks would be needed for using mod_rewrite in .htaccess files; in your case it is not required, because you can put everything in the Apache config. Moving rules from config to .htaccess is pointless and can only make things slower. However, there is an important difference between .htaccess and the Apache config — in .htaccess patterns in RewriteRule are matched against relative filesystem paths (which never start with /), while in the VirtualHost context these patterns are matched against the URL path after the hostname, which always starts with /. Therefore at least one of your rules is incorrect:

RewriteRule ^content/(js|css)/([a-z]+)-([0-9]+)\.(js|css)$ /content/$1/$2.$4

should be

RewriteRule ^/content/(js|css)/([a-z]+)-([0-9]+)\.(js|css)$ /content/$1/$2.$4

(note the additional slash in the beginning).

Mod_rewrite rule for images with query string

First add a RewriteBase, this will strip the /images/ part in the query string. You will get photo.jpg?w=... instead of /images/photo.jpg?w=....

Second add /images/ to the redirection, because your current redirection tells to go to http://mysite.com/thumbs/phpThumbs... instead of http://mysite.com/images/thumbs/phpThumbs....

This gives something like this:

 <IfModule mod_rewrite.c>
    RewriteEngine on
    RewriteBase /images/
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{QUERY_STRING} ^.+
    RewriteRule ([^\s]+(\.(?i)(jpg|png|gif|bmp))$) /images/thumbs/phpThumb.php?src=$1 [L,QSA]
 </IfModule>

Best Answer

Related Solutions

Tomcat – Apache2 – mod_expire and mod_rewrite not working in httpd.conf – serving content from tomcat

Mod_rewrite rule for images with query string

Related Topic