atom feed15 messages in org.apache.tomcat.usersRE: Force One page to not use SSL
FromSent OnAttachments
Rustad, AaronOct 28, 2002 4:48 pm 
Craig R. McClanahanOct 28, 2002 8:36 pm 
Nicholas PappasOct 29, 2002 7:44 am 
Rustad, AaronOct 29, 2002 7:45 am 
Srinadh KarumuriOct 29, 2002 9:17 am 
Pae ChoiOct 29, 2002 12:54 pm 
Schnitzer, JeffOct 29, 2002 3:56 pm 
Dan LipofskyOct 29, 2002 4:11 pm 
Justin RuthenbeckOct 29, 2002 4:19 pm 
Rustad, AaronOct 29, 2002 4:54 pm 
Craig R. McClanahanOct 29, 2002 9:55 pm 
Craig R. McClanahanOct 29, 2002 10:00 pm 
Bill BarkerOct 29, 2002 10:49 pm 
Craig R. McClanahanOct 29, 2002 10:54 pm 
Ralph EinfeldtOct 30, 2002 12:06 am 
Subject:RE: Force One page to not use SSL
From:Ralph Einfeldt (ralp@uptime-isc.de)
Date:Oct 30, 2002 12:06:28 am
List:org.apache.tomcat.users

I've once posted a skeleton to do that:

One option for you to work around this, would be (roughly) something like this:

- Create a hashtable that is global to the webapp. - Create a hashtable for each session - Store the session hashtable in the application Hashtable and use the session id as key - if (session.isNew() && (<RequestedSessionId> != null)) get the session hashtable by using the RequestedSessionId and store it with the new SessionId as key. - otherwise get the session hashtable by using the current session id. - Store your session variables in the session hashtable - make shure to remove every thing from the application hashtable whenever a session gets destroyed.

-----Original Message----- From: Rustad, Aaron [mailto:ARus@Online-can.com] Sent: Wednesday, October 30, 2002 1:55 AM To: 'Tomcat Users List' Subject: RE: Force One page to not use SSL

All I am asking is...does anyone know how to persist a session from HTTPs to HTTP. Any potential solutions are GREATLY appreciate...any other suggestions (even though they might be well-meaning) are discouraged.