There may be another alternative here if you are running Tomcat 5.5:
Set the proxyName, proxyPort, and emptySessionPath within your connector in
Tomcat's server.xml file.
In this case, I would set proxyName="iobis.marine.rutgers.edu",
proxyPort="80", and emptySessionpath="true".
This should res
Sander,
What progress I've made. I've gone from Apache-clueless to
answering my own questions.
Well, not quite answering but at least shedding some light. If I
use url rewriting our Apache 1.3 does not recognize the url because it
thinks the jsessionid is part of the context name, so
On Jan 26, 2007, at 10:48 AM, Wm.A.Stafford wrote:
I forgot to ask about one more aspect of this situation. When
we first realized that session cookies were not coming in to the
app we tried url rewriting and that did not resolve the problem.
Does Apache 1.3 do something to urls that
Sander,
I forgot to ask about one more aspect of this situation. When we
first realized that session cookies were not coming in to the app we
tried url rewriting and that did not resolve the problem. Does Apache
1.3 do something to urls that have an explicit session id?
ex. ip_and_contex
Sander,
Thanks a million for all your help!
-=bill
Sander Temme wrote:
On Jan 25, 2007, at 1:20 PM, Wm.A.Stafford wrote:
Sander,
Here is a cookie copied from Firefox cookie viewer when
the Apache+Tomcat machine was accessed from another machine.
Name: JSESSIONID
Content: 10FA6EB4F
On Jan 25, 2007, at 1:20 PM, Wm.A.Stafford wrote:
Sander,
Here is a cookie copied from Firefox cookie viewer when
the Apache+Tomcat machine was accessed from another machine.
Name: JSESSIONID
Content: 10FA6EB4F5B24CBA716A7F5DAD1F4B3F
Host: iobis.marine.rutgers.edu
Path: /OBISDEV
Sander,
Here is a cookie copied from Firefox cookie viewer when
the Apache+Tomcat machine was accessed from another machine.
Name: JSESSIONID
Content: 10FA6EB4F5B24CBA716A7F5DAD1F4B3F
Host: iobis.marine.rutgers.edu
Path: /OBISDEV
Send For: Any type of connecion
Expires: at end of session
The U
On Jan 24, 2007, at 11:00 AM, Wm.A.Stafford wrote:
A bit more info has emerged, the admin believes the Apache
version is 1.3.20.
Running httpd -v will take away any shred of doubt.
I'll see if there is any interest in moving to the latest
Apache but at this point I think that is p
Sander,
A bit more info has emerged, the admin believes the Apache version
is 1.3.20.
-=bill
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
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
th
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 look
Sander,
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
On Jan 23, 2007, at 6:51 AM, Wm.A.Stafford wrote:
Since the application works normally on Tomcat only, it seems pretty
certain that Apache needs to be configured to handle Tomcat session
management either by cookies or url rewriting or both.
You're probably losing the session cookie somehow,
We deployed our Tomcat-based system on an Apache+Tomcat site and
session management disappeared completely. Every Tomcat access to the
session resulted in the creation of a new session. Url rewriting did
not solve the problem.
This is apparently a well known situtuation. Searching around I fou
14 matches
Mail list logo
