Hi Tomcat-ers,
When I switch from http to https using URL rewriting (encodeURL(".."), with
cookies turned off, I loose my sessionId. Does any one know the trick so
that this does not happen?
Thanks,
Pat
getAbstract.com Ltd.
Patrick Brigger
Alpenquai 12/14
CH-6005 Luzern
Switzerland
Tel: +41
Hi,
Without cookies, I loose my session object when switching from http to https
using encodeUrl. Can anyone help?
Otherwise, it makes Tomcat really useless in real life applications, where
it is absolutely necessary to support customers that have cookies disabled.
Thanks,
Pat
(http or https) so when you switch from
http to https you will loose your session. Also the
port number will change, which changes the domain.
--- Brigger Patrick <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Without cookies, I loose my session object when
> switching from http to https
m
using cookies though)
Is your context the same on the secure and insecure ones
?
Can you provide an example of the link that you are using to
go between the insecure one and the secure one.
( and the link that it produces :) )
Thanks
David
Brigger Patrick wrote: >
> Th
When I try with cookies enabled, it works both on Netscape and IE 5.
Cookies disabled does not work on either.
Pat
-Original Message-
From: Mike Spreitzer [mailto:[EMAIL PROTECTED]]
Sent: Dienstag, 24. Juli 2001 19:13
To: [EMAIL PROTECTED]
Subject: Re: keeping sessions when switching fr
One simple solution, but works perfectly:
After the login process, save the login information in an object, for
instance a customer object.
session.putValue("customer", customer);
In your JSP page, read the customer object:
Customer customer = (Customer) session.getValue("customer");
Then do
ng the cross-protocol links (with
HttpServletResponse.encode[Redirect]URL())?
The only reason I ask is that it seems strange that it does OK with
cookies
but not with URL encoding: the code paths are similar, so I'd expect it
to
fail with both or succeed with both.
