I must apologize for having being wasting your time. After some deeper
investigations, it appears that the problem is due to at least two causes :
1) IE 5.5 (at least the version I installed) is configured by default to
reject cookies from a LAN. This is confusing because it does not take in
account configuration of previous versions (IE 5 in my case).
2) Most importantly the documentation for Servlet 2.2 API says :
public Cookie[] getCookies()
Returns an array containing all of the Cookie objects the client sent with
this request. This method returns null if no cookies were sent.
*** THIS IS NOT TRUE ***
If no cookie where sent, the method return a Cookie[] of lenght 0.
This can be quite confusing if a servlet test the return value against null.
Pierre-Yves Saumont
-----Message d'origine-----
De : A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]De la part de Pier
P. Fumagalli
Envoyé : jeudi 15 mars 2001 18:39
À : [EMAIL PROTECTED]
Objet : Re: Session tracking with IE 5.5
Saumont Pierre-Yves <[EMAIL PROTECTED]> wrote:
> The session ID is pushed as a cookie if cookies are accepted by the
browser.
> Of course, IE 5.5 accepts cookies. If the cookie is refused, the server
> generally use URL rewriting to track the session. The session ID coming
back
> to the server is refered as 'session ID being asked by the client' in the
> servlet documentation. No matter how it is achieved, Java session tracking
> will never work with IE 5.5. This is not really a problem if you are aware
> of it and do your own session tracking. (I use identified session tracking
> through PathInfo, storing HttpoSession objects in a HashTable. The main
> drawback is having to take care of invalidation while this could be
> automated with Java sessions.)
>
> The real concern is for developpers who are not aware of this problem and
> might rely on Java session tracking. It may take some times before they
> realise their servlets are not "compatible" with IE 5.5 clients.
>
> Another interesting question is "Why". Could it be a Microsoft decision ?
So, you're saying that IE-5.5 is apparently rejecting the jsessionid cookie
and ignoring when this parameter is URL-encoded in the request?
That _is_ weird. And I don't think M$ could actually handle if this was made
"on purpose" (imagine the flamewar)... I know though that I had problems
reported from BugZilla users (check out http://nagoya.javasoft.com/bugzilla)
having the same issues with something that is definitely not Java-Based (and
uses the same session tracking mechanism that servlet engines are supposed
to)... Can you check out if BugZilla works for you? I'll have someone @ Sun
to try out Sessions with IE-5.5...
Pier
--
----------------------------------------------------------------------------
Pier Fumagalli - Sun Microsystems Inc. - <mailto:[EMAIL PROTECTED]>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
