On Wed, Oct 15, 2008 at 7:25 AM, howard chen [EMAIL PROTECTED] wrote:
Thanks.
On Wed, Oct 15, 2008 at 7:19 PM, Eric Covener [EMAIL PROTECTED] wrote:
Only where they overlap and it's before 2.2, because it's undefined as
to which will run first.
In 1.3 you might be able to control it by
On Wed, Oct 15, 2008 at 7:07 AM, howard chen [EMAIL PROTECTED] wrote:
Hello,
On Wed, Oct 15, 2008 at 6:49 PM, Eric Covener [EMAIL PROTECTED] wrote:
On Wed, Oct 15, 2008 at 4:47 AM, howard chen [EMAIL PROTECTED] wrote:
Seems that Rewrite is done after the proxy? How to control the order then?
On Wed, Oct 15, 2008 at 4:47 AM, howard chen [EMAIL PROTECTED] wrote:
Seems that Rewrite is done after the proxy? How to control the order then?
in 2.2, rewrite will always happen first. In 2.0 it's unpredictable.
To control the order, use RewriteRule with [P] instead of ProxyPass
when it
Hello ,
I have the following config in httpd.conf:
my site is http://www.example.com (port 80)
==
RewriteEngine On
RewriteRule ^/$/cgi-bin/index.cgi
ProxyPass /cgi-bin/ http://www.example.com:9000/cgi-bin/
ProxyPassReverse /cgi-bin/
: [EMAIL PROTECTED] mod_rewrite, mod_proxy, order of execution?
Hello ,
I have the following config in httpd.conf:
my site is http://www.example.com (port 80)
==
RewriteEngine On
RewriteRule ^/$/cgi-bin/index.cgi
ProxyPass /cgi-bin/ http://www.example.com:9000
Thanks.
On Wed, Oct 15, 2008 at 7:19 PM, Eric Covener [EMAIL PROTECTED] wrote:
Only where they overlap and it's before 2.2, because it's undefined as
to which will run first.
In 1.3 you might be able to control it by AddModule ordering, but in
2.0 it may differ from system to system and you
Hello,
On Wed, Oct 15, 2008 at 6:49 PM, Eric Covener [EMAIL PROTECTED] wrote:
On Wed, Oct 15, 2008 at 4:47 AM, howard chen [EMAIL PROTECTED] wrote:
Seems that Rewrite is done after the proxy? How to control the order then?
in 2.2, rewrite will always happen first. In 2.0 it's unpredictable.
Hi all
I have a 2.2.8 server directing traffic (mod_rewrite) to a bunch of
back-end servers. We use a 499 status code from the back end to
indicate some sort of error condition to clients.
When the clients access the back-end directly, there is no problem.
When an error ocurrs, they get the 499.
Krist,
Ignore my last question, I was missing a quote. Thanks a bunch, that did it.
My final rule looks like:
RewriteCond %{REMOTE_HOST} ^192\.168\.220\.
RewriteRule ^(/.*)$ proxy:balancer://aquabrowser$1?c_loc=220 [QSA,L]
Krist van Besien wrote:
On Feb 11, 2008 3:25 PM, Travis
Thanks, I see what's going on now.
Here is what I've tried followed by the response on the backend server:
Case 1:
RewriteRule ^/(.*)$ proxy:balancer://aquabrowser$1?c_loc=220 [QSA,L]
GET /?c_loc=220\ HTTP/1.1 - Note I get a 500 error when trying to access
anything other then /.
Case2:
I see that now. Will check with the developers and see if they can work with
that. Thou, I'd still like to know why mod_rewrite is behaving funny.
Mike Cardwell wrote:
mod_proxy should add an extra HTTP header to the request called
X-Forwarded-For which you can parse to retrieve the IP
mod_proxy should add an extra HTTP header to the request called
X-Forwarded-For which you can parse to retrieve the IP address from.
Note, this can contain multiple IPs if there are several proxies on
route so make sure you parse it correctly.
Regards,
Mike
Travis Sidelinger wrote:
We have
We have used both mod_rewrite and mod_proxy successfully in numerous
configurations. Put them together and they don't seem to like each other.
We have a working production mod_proxy_balancer configuration for two backend
web servers that is working great, except... The backend web servers need
On Feb 11, 2008 3:25 PM, Travis Sidelinger [EMAIL PROTECTED] wrote:
RewriteRule ^/(.*)$ proxy:balancer://aquabrowser$1c_loc=220 [QSA,L]
# I
get 404 Error: GET //cd/READMEc_loc=220%22?test=1 HTTP/1.1 in the logs of
the
backend server.
You append c_loc=220 to the URL, and then append
We have a working production mod_proxy_balancer configuration for two
backend web servers that is working great, except... The backend web
servers need the IP address of the clients to identify their location.
Yes, I had suggested just adding a location drop down so that users
could select
Unfortunately it's not my client, but Nokia's EAIF MMSC (emulator in this
case).
Like I said, I've coded my application to the protocol (EAIF) and it works.
I only need to add apache httpd in between in order to restrict access to
the application (by IP address range).
The response headers
On 25/07/07, Daniel JavaDev [EMAIL PROTECTED] wrote:
Unfortunately it's not my client, but Nokia's EAIF MMSC (emulator in this
case).
Like I said, I've coded my application to the protocol (EAIF) and it works.
I only need to add apache httpd in between in order to restrict access to
the
On Wed, 25 Jul 2007 10:59:33 +0100
Daniel JavaDev [EMAIL PROTECTED] wrote:
Unfortunately it's not my client, but Nokia's EAIF MMSC (emulator in
this case).
Like I said, I've coded my application to the protocol (EAIF) and it
works. I only need to add apache httpd in between in order to
Nick,
works out the header was actually being added by protocol.c (in
ap_set_content_length)
I've fixed it for what I needed by simply commenting out the body of that
method. This keeps the EAIF MMSC happy and this httpd instance will only be
used for this purpose anyway.
Not sure what the
Hi all,
I have the following rules on my apache 2.2.4 config:
RewriteEngine on
RewriteRule ^/someURL http://anotherURL [P]
where someURL is the a publicly available url, and anotherURL is a private
url (localhost on another port). This setup is for restricting access to an
application server.
On 25/07/07, Daniel JavaDev [EMAIL PROTECTED] wrote:
Hi all,
I have the following rules on my apache 2.2.4 config:
RewriteEngine on
RewriteRule ^/someURL http://anotherURL [P]
where someURL is the a publicly available url, and anotherURL is a private
url (localhost on another port). This
Hi,
I was presented with the seemingly straightforward task of converting URLs such
as:
http://cellularmanagerpp.aliant.net/myProg?param1=val1url=http://cellularmanagerpp.aliant.netparam3=val3
to:
http://erie:9090/myProg?param1=val1url=http://erie:9090param3=val3
Attempt 1
---
On 6/22/06, Chris Price [EMAIL PROTECTED] wrote:
Joshua Slive wrote:
This question was recently asked and answered:
http://mail-archives.apache.org/mod_mbox/httpd-users/200606.mbox/[EMAIL
PROTECTED]
Unfortunately, my backend servers are Coldfusion on IIS (garbage, I
know), so
@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] mod_rewrite mod_proxy %2F in URL
Hello.
Thanks a lot for your tip but I think this will not help in our case.
I was not able to test if the switch works but your explanation gives me the
hint that it takes place in the mod_rewrite part
Stockhausen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 8:59 PM
To: Axel-Stéphane SMORGRAV; users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] mod_rewrite mod_proxy %2F in URL
Hello.
Thanks a lot for your tip but I think this will not help in our case.
I was not able to test
;
}
Could you try adding the NE flag to your rewrite rule and see what happens ??
-ascs
-Original Message-
From: Markus Stockhausen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 5:57 AM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] mod_rewrite mod_proxy %2F in URL
-
From: Markus Stockhausen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 13, 2006 5:57 AM
To: users@httpd.apache.org
Subject: [EMAIL PROTECTED] mod_rewrite mod_proxy %2F in URL
Hello.
We used Apache 2.0.54 as a reverse proxy for an internet webmail access with
the following rewrite rule
13, 2006 2:34 PM
To: users@httpd.apache.org; Markus Stockhausen
Subject: RE: [EMAIL PROTECTED] mod_rewrite mod_proxy %2F in URL
I thought there was a flag blocking URL escaping in rewrite rules, but I am
actually unable to find it in the module documentation. Checking the code,
however, I found
Hello.
We used Apache 2.0.54 as a reverse proxy for an internet webmail access with the
following rewrite rule:
AllowEncodedSlashes On
RewriteEngine on
RewriteRule
/(.*)/MessagePart/(.*)/(.*)/(.*)-H.txt
http://127.0.0.1:8100/$1/MessagePart/$2\%2F$3/$4-H.txt [P]
It is essential for the
29 matches
Mail list logo
