httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wm.A.Stafford" <>
Subject Re: [users@httpd] Apache + Tomcat = no session management
Date Wed, 24 Jan 2007 19:00:07 GMT

    A bit more info has emerged, the admin believes  the Apache version 
is  1.3.20.


Wm.A.Stafford wrote:
> Sander,
>    Good news and bad news.  The admin confirmed that Apache is being 
> used as a proxy but she does not know what version of Apache is being 
> run but she thought it was 1.2.  I looked around on the server and the 
> date of Apache.exe is 6/23/2002.  Is there a file that is delivered 
> with the executable that would have the version number?
>    I'll see if there is any interest in moving to the latest Apache 
> but at this point I think that is probably not an option because there 
> are a lot of other users of this system and they would all have to buy 
> in.  So I will need to proceed with configuration of the existing 
> version.
>    -=bill
> Sander Temme wrote:
>> On Jan 23, 2007, at 1:30 PM, Wm.A.Stafford wrote:
>>>    Thanks for replying to my query.  I don't really know anything 
>>> about Apache.  How would I go about determining how Apache and 
>>> Tomcat interact?  I have the httpd.conf file for the Apache in 
>>> question, can  I  tell from that?
>>>    I have looked through the file and I do not see mod_jk being 
>>> loaded so I think we can rule out that.
>>>    I see the lines below in httpd.conf does this mean communication 
>>> is  via HTTPProxy? (our app is OBISDEV)
>>>    ProxyPass /OBISBETA http://localhost:8082/OBISDEV
>>>    ProxyPassReverse /OBISBETA localhost:8082/OBISDEV
>> Yes, that looks promising. So, when you connect to your application, 
>> you type in the browser something like:
>> http://yourhostname/OBISBETA/somewebapppath
>> Any request that starts with /OBISBETA will be forwarded to the 
>> latter URL, with whatever came after /OBISBETA (/somewebappath in 
>> this case) tacked on.
>> If the web app decides to write a cookie to the browser, it may 
>> choose to include a path.  Tomcat thinks it's running at /OBISDEV, 
>> which is different from the path seen by the browser.
>> When the browser sends the next request, it'll send any cookie along 
>> that it has cached for the hostname and path under consideration. 
>> Since the browser connects to a different path (/OBISBETA instead of 
>> /OBISDEV), your cookie wont't get sent which your Tomcat will see as 
>> an opportunity to create a brand new session all over again.  If you 
>> open your browser's cookie cache, you should find the orphaned cookie 
>> that you received but didn't send back.
>> Which version of Apache are you using? As of Apache 2.2, we have a 
>> configuration directive 'ProxyPassReverseCookiePath' that can rewrite 
>> such a Cookie path on the proxy. If you are running Apache 2.2.x, 
>> have a look at
>> (hint: put ProxyPassReverseCookiePath /OBISDEV /OBISBETA next to the 
>> ProxyPassReverse directive and restart your Apache)
>>>    I'm sorry to be so clueless but I have absolutely no experience 
>>> with Apache.
>> That's OK, we're here to help.  If you need any more info, perhaps 
>> you can paste us the contents of such an orphaned cookie... don't 
>> worry about the contents (a session ID is just random data as far as 
>> we are concerned), but the cookie name (probably JSESSIONID), domain 
>> and path would be good info.  If you can't find it, clear your 
>> browser cache (on your test machine, don't want you to lose all your 
>> saved logins), access your app and then look what the cat dragged in.
>> S.
>> Open Source Software Consultant
>> PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF
> ---------------------------------------------------------------------
> 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:

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