https and http are on different ports and therefore count as different
hosts. I wouldn't mind knowing how you got that working, but I think I can
code round it by not storing the basket within the HttpSession.
Dave
[EMAIL PROTECTED]
-----Original Message-----
From: Alistair Hopkins [mailto:[EMAIL PROTECTED]]
Sent: 08 February 2001 14:31
To: [EMAIL PROTECTED]
Subject: RE: HttpSession across virtual hosts
The http // https comparison doesn't work as cookies are sent or not
depending on the host, not on the protocol.
So if I have a valid session_id in a cookie in http, that will still be sent
when I switch to https.
So I can either have a common pool of current cookies if my https server is
seperate from my http server (seems a hard way to do it) or I just access
the software (eg Tomcat) via a webserver (eg apache) through either protocol
and the session continues without complaint.
Unless I did something complicated without noticing, of course...
-----Original Message-----
From: Randy Layman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 08, 2001 1:13 PM
To: [EMAIL PROTECTED]
Subject: RE: HttpSession across virtual hosts
What I've seen done, which doesn't necessarily make it secure, it to
send some form of CartID. This ID identifies the Cart in some shared back
end data store. Usually these are large numbers that contain enough
information to determine if its a possible real value, or a number someone
made up. If its something that someone made up, usually their IP is locked
out for a certain amount of time or a session field is set that doesn't
allow them in as long as that same session is valid.
Randy
-----Original Message-----
From: David Oxley [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 08, 2001 8:08 AM
To: '[EMAIL PROTECTED]'
Subject: RE: HttpSession across virtual hosts
>I sort-of understand what you're doing, but I'm not clear on a couple of
details.
>What do you mean when you say you've "coded a request"? How exactly is
>the session ID passed from the original host to the new host, is this by a
>form field embedded into the HTML, or is it all on the server side?
Like URL-Encoded session management. The host passes our session id back to
the server when changing hosts so that it can be connected to the new
HttpSession.
Doesn't normal session management have exactly the same problem. When
writing an E-Commerce system the basket is normally chosen on an unsecure
host and then the user is put on to a secure host to checkout their
products. You need to be able to id the user between the two hosts. There
has to be a 'secure' way of doing this?!?!
Dave
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
