Hi Benoit,
Alex on this group suggested me to go with ProxyPass instead of
using rewrite rule. I tried that and it worked for me.
Here is the text Alex had send me - (Maybe it would help you as well)
<VirtualHost 172.29.11.12:80>
ServerName www.in.abc.org
ProxyVia off
Redirect / http://www.in.abc.org/wps/portal
<Location /wps>
ProxyPass http://www.dev01.abc.org:9081/wps
ProxyPassReverse http://www.dev01.abc.org:9081/wps
</Location>
</VirtualHost>
Works for me, should work for you too. www.dev01.abc.org could be an
alias for www.in.abc.org or vice-versa since from what I understand,
they both share the same IP address.
As pointed out previously, your problem lies in the domain of the
cookies served by WAS. My guess is that those cookies are in the
dev01.abc.org domain, whereas the browsers access the application in the
in.abc.org domain in which the cookies would not apply.
As all the users are located only in the in.abc.org domain, you can
change the domain name of WAS through the WAS Administrative Console
Security->Authentication Mechanisms->LTPA. Set the value of the "Domain
Name" field to "in.abc.org". This would set the domain of the JSESSIONID
cookie to a value which would allow the client browsers to include the
cookie in the requests.
If you don't, the browser will not include the cookies in the requests.
Another way of doing this would be to use the
ProxyPassReverseCookieDomain directive:
ProxyPassReverseCookieDomain .dev01.abc.org .in.abc.org
Unfortunately this directive has not been implemented in any release of
Apache 2.0. You would need to apply patch 11915 (see Bugzilla bug report
10722).
In order to debug such problems, if you use MSIE I would strongly urge
you to use a tool like HTTPWatch (http://www.httpwatch.com/default.htm)
which will allow you to see the headers and cookies in requests as well
as in responses, whether a page was served from cache, etc. It gives you
a very nice insight into all requests and responses. I you use Mozilla,
I understand there is a similar feature called something like "Live HTTP
Headers".
Another way of investigating such problems might be using a network
sniffer like Ethereal, or a proxy like Burp. That's would be my second
choice though, because a browser plug-in is a lot more user-friendly.
For a little cookie tutorial, look at
http://www.httpwatch.com/httpgallery/cookies/.
_Rajiv
-----Original Message-----
From: benoit.herard@xxxxxxxxxx [mailto:benoit.herard@xxxxxxxxxx]
Sent: Friday, August 12, 2005 6:34 PM
To: Ranjan, Rajiv
Subject: Apache Reverse proxy
Hi Rajiv,
I'm searching over the web about my own problem with using apache as a
reverse proxy and obviouly you've got the same problem as me.
"How to use apache as cookie gateway ?"
(The docs I found about my problem was always your case)
After running google a lot and testing a lot, I think that apache 2.0 is
not able to do so. The mod_rewrite can only work on URL and not on the
content of the HTTP flow.
Did you finally succed to solve the problem without using Apache 2.1
alpha
version ?
If Yes, what's the solution ?
Best regards Benoit
------------------------------------------------------------------------
-----------------------------------------------------
Benoit HERARD
EQ/PIT/SIS/OSS/CPM
rue Latouche Lambert
35510 CESSON-SEVIGNE
FRANCE
Tel : +33 (0)2 23 28 35 20
-------------------Warning------------------------
This e-mail is from outside Tesco - check that it is genuine. Tesco may
monitor and record all e-mails.
---- Disclaimer ----
This is a confidential email. Tesco may monitor and record all emails. The views expressed in this email are those of the sender and not Tesco.
Tesco Stores Limited, Tesco House, Delamare Road, Cheshunt, Herts, EN8 9SL: company number 519500.
---------------------------------------------------------------------
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
|