Thanks, my version of tomcat 5.5.26. My mistake I was looking at tomcat 3.3
documentation:
http://tomcat.apache.org/tomcat-3.3-doc/tomcat-apache-howto.html
http://tomcat.apache.org/tomcat-3.3-doc/tomcat-apache-howto.html .
Yes defining contexts in the Server.xml is discouraged but I'm doing it
an
I have multiple contexts that are defined for a given host in my server.xml
each context I would like to start up in its own jvm, for dll and
enviornment variable reasons.
Here's an example of my server.xml:
(which I'm not using) on older versions (which I'm not using).
I'll try the cookies enabled angle thanks.
Christopher Schultz-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Michael,
>
> Michael Dehmlow wrote:
>> The new session println
ch
says to me that tc is ignoring the url encoded sessionid. I've tried every
variation I can think of can someone point me in the direction of the
tomcats source 8(
Christopher Schultz-2 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Micha
Alright now I have another problem which is baffling me:
I have:
<%@ page session="true" %>
'<%=response.encodeURL("test/") %>'
in a jsp page.
the result is always 'test/'
so i tried forcing:
'<%="test;jsessionid="+request.getSession().getId() %>'
And the result looks like i expect it too
But w
in the
context file. And simply encode all URLs.
Michael Dehmlow wrote:
>
> Hello I'm looking for a way to force url session tracking regardless of
> whether the user has cookies enabled. My thoughts right now are to create
> a session filter that deletes the cookie on the way
Hello I'm looking for a way to force url session tracking regardless of
whether the user has cookies enabled. My thoughts right now are to create a
session filter that deletes the cookie on the way out the door. if this
seems like a good idea who should I go about deleting the the cookie.
--
Vie
