httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Axel-St├ęphane SMORGRAV <>
Subject RE: [users@httpd] Reverse proxing through apache where backend server uses cookie authentication
Date Thu, 21 Jul 2005 13:10:38 GMT
Good news: you probably do not need mod_rewrite.
Try this:

	ProxyVia off
	Redirect /

      <Location /wps>

Works for me, should work for you too. could be an alias for
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 domain, whereas the browsers access the
application in the domain in which the cookies would not apply.

As all the users are located only in the 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 "". 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:


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 ( 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


-----Original Message-----
From: Ranjan, Rajiv [] 
Sent: Thursday, July 21, 2005 8:20 AM
To: Axel-St├ęphane SMORGRAV
Subject: RE: [users@httpd] Reverse proxing through apache where backend server uses cookie

Hi Axel,

Thank you for replying. I am still struck with the issue.
As your mail suggests, you might already have done something similar to what I am trying to
do. So, I will explain you the entire scenario in detail.
Maybe you would be able to help me.

I have an application running on WebSphere Portal server in domain "" and I have
my proxy server in "".

As all the users who would be accessing the application are in ""
domain, my primary aim at getting a proxy is that it can do the url rewriting and the users
wouldn't have to give the fully qualified name of the app server machine in the browser to
access the application.

I also tried installing apache on my app server machine (i.e. on "" domain machine)
and tried to see if its working but it doesn't work there either (I have attached the conf
for this).

I am new to apache and url rewriting, can you please tell me if I am doing something wrong
here or do I also need to do some changes in WebSphere console. 

My rewriting configuration is as follows - 

	ProxyVia on
	RewriteEngine on
	RewriteLog logs/rajiv_rewrite.log
	RewriteLogLevel 9
	Redirect /

	RewriteRule ^/(.*)/myportal(.*){REQUEST_URI}/http/$1



The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message