httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joydeep Bakshi <joydeep.bak...@netzrezepte.de>
Subject Re: [users@httpd] .htaccess {QUERY_STRING} and issue with append a value
Date Mon, 27 May 2013 07:04:36 GMT
Hello Tom,

sorry for the wrong implementation of the rules.

This time I have done it as per requirement

actual url    http://www.mydomain.com/index.php?id=7&artId=7572&doi=10.5414/ALP33211

it should be  http://www.mydomain.com/index.php?id=7&artId=7572&doi=10.5414/ALP33211&L=5

The &L=5 has to be appended

.htaccess
=========

RewriteCond %{QUERY_STRING}  ^id=7&artId=7572&doi=10.5414/ALP33211$
RewriteRule index.php index.php?L=5 [QSA,R=301]

Log
=====
RewriteCond: input='http://www.mydomain.com/index.php?id=7&artId=7572&doi=10.5414/ALP33211'
pattern='highest-credit' [NC] => not-matched
RewriteCond: input='' pattern='^id=7&artId=7572&doi=10.5414/ALP33211$' => not-matched

When the require patter need to be compared the input becomes null !!!
Could you kindly explain ?

Thanks





On 24-May-2013, at 8:50 PM, Tom Evans <tevans.uk@googlemail.com> wrote:

> On Fri, May 24, 2013 at 3:37 PM, Joydeep Bakshi
> <joydeep.bakshi@netzrezepte.de> wrote:
>> 
>> 
>> On 24-May-2013, at 6:46 PM, Tom Evans <tevans.uk@googlemail.com> wrote:
>> 
>>> On Fri, May 24, 2013 at 2:03 PM, Joydeep Bakshi
>>> <joydeep.bakshi@netzrezepte.de> wrote:
>>>> It was level 5 and now I have set level 9.
>>>> From log it seems that the pattern is blindly applied to every link rather
>>>> than matching the query_string
>>>> 
>>>> applying pattern '^ALP33211$' to uri 'index.php'
>>>> applying pattern '^ALP33211$' to uri
>>>> 'uploads/repository/02/1276_cn74_1001.gif'
>>>> applying pattern '^ALP33211$' to uri
>>>> 'fileadmin/templates/images/btnAddCart.png'
>>> 
>>> That cannot be correct, At log level 9, the rewrite log would contain
>>> a mass of information for a single request, where as you are showing
>>> only one line per request.
>>> 
>>> Please do not trim the log contents or decide what is important and
>>> what is not, show the entire rewrite log for a single request that
>>> should be rewritten.
>>> 
>>> 
>>>> ……..
>>>> ….
>>>> 
>>>> where te ruleset I have at .htaccess is
>>>> 
>>>> RewriteCond %{QUERY_STRING} ^Id=7572&doi=10.5414/ALP33211$
>>>> RewriteRule ^/ALP33211$  /ALP33211&L=1 [R=301]
>>>> 
>>>> The actual url is
>>>> http://www.mydomain.com/index.php?id=7&artId=7572&doi=10.5414/ALP33211
>>>> 
>>>> and it has to become
>>>> 
>>>> http://www.mydomain.com/index.php?id=7&artId=7572&doi=10.5414/ALP33211&L=5
>>>> 
>>> 
>>> The URL is "/index.php". Everything else is part of the query string.
>>> Your RewriteRule is predicated on the URL "/ALP33211", and so is
>>> ignored. In a .htaccess, you must also not specify the leading '/'
>>> either.
>>> 
>>> Please do show the correct log entries, but this should work (untested):
>>> 
>>> RewriteCond %{QUERY_STRING} ^Id=7572&doi=10.5414/ALP33211$
>>> RewriteRule index.php index.php?L=5 [QSA,R=301]
>>> 
>>> Cheers
>>> 
>>> Tom
>> 
>> Hello Tom,
>> 
>> applied your rules  at .htaccess but no luck.
>> 
>> The log says as follows
>> 
>> 122.176.30.116 - - [24/May/2013:16:02:13 +0200] [www.mydomain.com/sid#7f251146d330][rid#7f251191fa18/initial]
(4) [perdir /srv/www/htdocs/mydomain/] RewriteCond: input='id=7&artId=7572&doi=10.5414/ALP33211'
pattern='^Id=7572&doi=10.5414/ALP33211$' => not-matched
> 
> 
> Seems pretty clear, don't you think?
> 
> input='id=7&artId=7572&doi=10.5414/ALP33211'
> pattern='^Id=7572&doi=10.5414/ALP33211$'
> 
> Cheers
> 
> Tom
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 


Mime
View raw message