I assume that what is happening is that privateserver issues a redirect to itself which is not rewritten by the reverse proxy, i.e. the Location header of the HTTP 302 is not rewritten.
This happens because you do not have the appropriate ProxyPassReverse in your configuration.
In order to get more insight into exactly what is going on I suggest that you try using LiveHTTPHeaders with Firefow, or HTTPWatch with IE. These tools will enable you to see the values of all headers in the requests as well as in the responses, and you will be able to modify your ProxyPassReverse statements accordingly.
If you cannot figure it out, please post a trace from LiveHTTPHeaders.
-ascs
-----Original Message-----
From: Frederick, Fabian [mailto:Fabian.Frederick@xxxxxxxxxxxxx]
Sent: Friday, December 16, 2005 12:08 PM
To: users@xxxxxxxxxxxxxxxx
Subject: RE: [users@httpd] ProxyPassReverseCookieDomain
Thanks Axel ! It works now :) But a major problem appears :
Here's the scenario :
Http//publicserver displays authentification box from private server :
Entering name and password for privateserver at publicserver (here before sending, netstat gives no direct link to privateserver).
When completed correctly, client receives the cookie BUT appears in address http//privateserver page Netstat gives now a direct link to private server ... Is there a way to avoid this ? IOW to keep this 'tunnel' client -> public server -> private server ?
Regards,
Fabian
-----Message d'origine-----
De : Axel-Stéphane SMORGRAV [mailto:Axel-Stephane.SMORGRAV@xxxxxxxxxxxxxx]
Envoyé : mardi 13 décembre 2005 14:29
À : users@xxxxxxxxxxxxxxxx
Objet : RE: [users@httpd] ProxyPassReverseCookieDomain
After having checked the CHANGES_2.0 file, it seems like ProxyPassReverseCookieDomain has not made it into the 2.0.55 distribution. If you need that functionality you should therefore apply the patch attached to Bugzilla BR 10722 (patch 11915) and recompile the appropriate modules.
The order of parameters for ProxyPassReverseCookieDomain (and ProxyPassReverseCookiePath) is the same as for ProxyPass.
-ascs
-----Original Message-----
From: Frederick, Fabian [mailto:Fabian.Frederick@xxxxxxxxxxxxx]
Sent: Tuesday, December 13, 2005 11:36 AM
To: users@xxxxxxxxxxxxxxxx
Subject: [users@httpd] ProxyPassReverseCookieDomain
Hi,
Does Apache 2.0.55 able to reverse proxy cookies using ProxyPassReverseCookieDomain ?
Maybe someone has a link to a sample config somewhere ? I don't understand ProxyPassReverseCookiePath parameter ...
Best regards,
Fabian
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|