Mike. Dude. That IS the way to do it.
1) check to see if you ACTUALLY GET the 2 sessions (if you can get them, do
a session.toString() to see that they are not the same session indeed)
2) you should be sending the serialized data from the unsecure session into
the secured session:
if you are
PROTECTED]
Betreff: Re: still fighting HTTP HTTPS problem
Mike. Dude. That IS the way to do it.
1) check to see if you ACTUALLY GET the 2 sessions (if you can get them, do
a session.toString() to see that they are not the same session indeed)
2) you should be sending the serialized data from
Sorry Mike. I didnt intend to put you off. I was just trying to re-enforce
that you were doing the correct thing.
Cheers
- Original Message -
From: Michael Wilimsky [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 11, 2001 8:15 AM
Subject: RE: still fighting HTTP HTTPS problem
I'm using a standalone container, and I find that everything works
transparently (only one session) if I resort to hard coding the scheme.
Right now, I'm doing this in the Struts-config.
forward name=standard
path=http://data.wxxi.org/wxxi-gavel/register/logon.jsp/
forward name=secure
Ted,
You can collapse your code down to this:
return mapping.findForward(secureMode ? secure : standard);
by adding redirect=true to your secure forward definition in struts-config.
--
Martin Cooper
At 01:25 PM 5/11/01, Ted Husted wrote:
I'm using a standalone container, and I find that
Are you saying that an http request can be forwarded to an https
request? That doesn't make sense; if the browser doesn't have an https
session setup, the server can do whatever it wants to resolve the request
translation. You have to redirect to go from an http request to an https
request.
ActionForward actionForward = new ActionForward(url,true);
The forward here is a bit of a misnomer. Using true forces a
redirect.
Ian Kallen wrote:
Are you saying that an http request can be forwarded to an https
request? That doesn't make sense; if the browser doesn't have an https
7 matches
Mail list logo