On 1/16/06, Mark Lowe [EMAIL PROTECTED] wrote:
The first page to be served up by the container will append the sessionid to
the url. If cookies are enabled on the client (browser) then in subsequent
requests the jsessionid will be stored in a cookie..
A redirect in your welcome file should do
Helo
There are three main methods for maintaing the session in HTTP
(according to the java servlets standard): cookies, ssl session and
URL rewriting. The jsessionid parameter is just a way of ensuring the
session when the servlet container has yet to find out if the user
agent will
Why would appending the session ID to the URL prevent Apache from
passing the request to Jrun? Sounds like an Apache mis-configuration to
me. I don't know how you configure Apache to 'recognise [something] as a
jrun file' but that's what you need to be looking at.
L.
Zoran Avtarovski wrote:
I'm hoping someone here can help me with this.
I'm getting inconsistency on this issue and googling hasn't helped.
I'm running a struts app on OS X with Jrun 4 and Apache 2. When I use
c:redirect url=/general/getInfo.do / in the index.jsp file it appends
the jsessionid to it and apache doesn't
4 matches
Mail list logo
