From what I understand of how cookies work, they are specified for a
particular site. I would assume that a browser would see
hostname.domainname.com:8000 and hostname.domainname.com as being two
separate sites, and so cookies it recieves from one will not be sent to the
other. Whatever, I would expect this to be a browser issue rather than a
server one.
Dave
> -----Original Message-----
> From: Ball, Stephen [mailto:[EMAIL PROTECTED]]
> Sent: 08 September 1999 13:22
> To: [EMAIL PROTECTED]
> Subject: Cookies For Session Management, Is It JRun?
>
>
> Hello All,
> I don't know if this has already been discussed, but
> I am constantly
> running into a "situation". I am maintaining a base url
> throughout my
> session. (hostname.domainname.com:8000) I rely on this url
> for all types
> of navigation. On occasion, myself or another user will use
> an equivalent
> valid machine name for our intranet, be it an IP address or
> just a local
> hostname to access the site. As session objects are being
> "put" and then
> "get", I get all sorts of null session objects. After
> checking it out, I
> realized that the IP address, the local hostname, the fully
> qualified name
> are all maintaining different sessions. Therefore all
> session objects under
> the IP address are maintained under a seperate cookie from the session
> objects maintained under the hostname..... Is this part of
> the spec? Is
> this a JRun issue only? Do I just need to come up with a
> best practice for
> coding around this?
>
> Thanks In Advance,
>
> Stephen C. Ball
> Consultant, Software Architects, Inc.
> [EMAIL PROTECTED]
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
