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 sho
#x27;t get any answer, so it propably won't be in the next
> webtier release (Servlet 2.5/ JSP 2.1).
>
> Bernhard
>
> > -Ursprüngliche Nachricht-
> > Von: Marcelo Morales [mailto:[EMAIL PROTECTED]
> > Gesendet: Samstag, 14. Januar 2006 19:50
>
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 accep
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:
4 matches
Mail list logo
