I care because I have to test again at the top of the rules for the rewritten
URIs to say "ok their fine now, get out", or they get screwed up by the
re-evluation of the same rules for some instances.
I have read further that I need to place the rules inside a to
prevent this, I used a wrot
On Fri, Feb 8, 2013 at 9:28 PM, Eric Covener wrote:
> On Fri, Feb 8, 2013 at 9:23 PM, Coughlin, Michael J
> wrote:
>> I had many rewrite rules in .htaccess. I discovered they were being
>> reevaluated with an internal direct after a rewrite. I also read that this
>> does not happen if you pla
On Fri, Feb 8, 2013 at 9:23 PM, Coughlin, Michael J
wrote:
> I had many rewrite rules in .htaccess. I discovered they were being
> reevaluated with an internal direct after a rewrite. I also read that this
> does not happen if you place the rules in the httpd.config file.
>
> So I did, I kille
I had many rewrite rules in .htaccess. I discovered they were being
reevaluated with an internal direct after a rewrite. I also read that this
does not happen if you place the rules in the httpd.config file.
So I did, I killed the .htaccess file to be sure, and sure enough, the internal
redir
What a disaster, the htaccess rules run twice. no wonder.
It's easy enough to catch on a second pass now that I know what's happening,
but this little subtle point could be made a BIG point in the apache
documentation for htaccess.
Thanks for the clue about the repass.
__
I am trying to proxy a connection from ifolder client to our ifolder server.
Here are the proxypass statements:
ProxyPass /ifolder https://192.168.123.4/ifolder
ProxyPassReverse /ifolder https://192.168.123.4/ifolder
With just those statements, i get these errors in the apache pr
Sorry i mean
>> RewriteRule ^(t.*)$ test.php?req=$1 [NC,END]
The flags END are stronger than L and may be you loop from testing123 to
test.php both matching
Le 8 févr. 2013 à 22:46, Boubouch a écrit :
> Hi,
>
> Could you try this
>
>> RewriteRule ^(t.*)$ test.php?req=$1 [NC,END]
>
>
> Le
END is not a valid flag. That generates a server error.
From: Boubouch [boubouc...@gmail.com]
Sent: Friday, February 08, 2013 4:46 PM
To: users@httpd.apache.org
Cc: users@httpd.apache.org
Subject: Re: [users@httpd] RewriteRule problem
Hi,
Could you try t
Hi,
Could you try this
> RewriteRule ^(testing.*)$ test.php?req=$1 [NC,END]
Le 8 févr. 2013 à 22:19, "Coughlin, Michael J" a
écrit :
> The request:
>
> www.mysite.com/testing123
>
> The rule:
>
> RewriteRule ^(testing.*)$ test.php?req=$1 [NC,L]
>
> test.php properly renders the querystri
The request:
www.mysite.com/testing123
The rule:
RewriteRule ^(testing.*)$ test.php?req=$1 [NC,L]
test.php properly renders the querystring "req=testing123" (its only purpose to
verify the querystring)
BUT,
RewriteRule ^(t.*)$ test.php?req=$1 [NC,L]
gives me: "req=test.php".
I don't get
How are you measuring the load on the backend Tomcats?
On Feb 8, 2013, at 7:57 AM, aparna Puram wrote:
>
> Hello All,
>
> We have a apache server that acts as a load balancer for 6 backend tomcat
> servers.
>
> However, If I compare the load on all the servers, there is a drastic
> differen
Hello All,
We have a apache server that acts as a load balancer for 6 backend tomcat
servers.
However, If I compare the load on all the servers, there is a drastic
difference between the no of hits on all the servers.
We are using lbmethod =bybusyness.
Please help, If there are any tools to che
Hi,
Thanks for the reply.
It looks that Apache is handling the malformed params properly, but
not with phusion passenger module.
I've already created an issue on PP project.
If this will not get resolved I will create a simple rule with mod_taint
Best regards
Jakub Nieznalski
2013/2/5 Nick Kew
On Thu, 7 Feb 2013 23:40:50 -0600
yogesh hingmire wrote:
> $ httpd -V
>
> Am i missing something
'which httpd'
If that doesn't have you kicking yourself, you need to get
to grips with the operating system concept of paths.
--
Nick Kew
14 matches
Mail list logo
