How would you do that if you are using Form authentication
and the web.xml file directs them to a loginpage before they
access the index.jsp
Have the same problem and found that If they accept session cookies
then all is ok
Your help would be greatly appreciated.
-Original Message-
Ralph,
Thanx for your advice but this is likely to be a bug in TC 4.0.2 that cannot be
too hard to fix. I just found-out that it only affects SSL, which I guess is the
reason no one has seen it before.
URL rewriting is a possibility but our app will get ugly, so I prefer to
launch without Mac.
Ralph,
I got the impression from your previous posts, that
the browser is the source not tomcat.
Well This is matter of taste. As IE 5 is the current Mac release and
IE is relatively popular even by Mac-user's, I believe that TC should
adopt to IE 5 rather than the revse. A *really*
I haven't been following this thread but it seems like you are
saying that Tomcat should be modified to work correctly with IE 5. The
problem with that is that Tomcat is an reference implementation of a
particular spec (JSP/Servlet) which dictates how things have to work - it is
the
Randy,
I don't know if Mac IE 5 is doing something *outside* of the cookie-specification
(which governs this rather than the servlet specification), but I'm pretty sure that
the original Apache-server handles this differently than Tomcat. Do you know
any Apache SSL-site using session-cookies
On Fri, 8 Mar 2002, Randy Layman wrote:
I haven't been following this thread but it seems like you are
saying that Tomcat should be modified to work correctly with IE 5. The
problem with that is that Tomcat is an reference implementation of a
particular spec (JSP/Servlet) which
From: Anders Rundgren [mailto:[EMAIL PROTECTED]]
Well This is matter of taste. As IE 5 is the current
Mac release and
IE is relatively popular even by Mac-user's, I believe that TC should
adopt to IE 5 rather than the revse. A *really* strange thing is that
persistant cookies work.
Ralph, at this stage we can just guess as it does not *have* to be a browser bug.
Particularly as other web-servers most likely handles this differently.
I have verified that IIS does this OK but that was hardly a surprise :-).
I will now perform some deeper investigation by writing a small
I believe that Joe is right: the JSP/Servlet spec is a server-side spec, and
the servers serve (forgive the pun) the browser community. A spec that
actually excludes even 1% of the browsers is suspect, IMHO. (And I'm not
sure I believe that the JSP/Servlet spec could possibly be the culprit --
I've been watching this thread with some interest, because I have had no
difficulty using cookie-based sessions on Tomcat 4.0.1 with Mac OS X and IE.
Judging from the headers you reproduced in your email, it would appear the
Tomcat has been configured in such a way as to treat the session cookie
Dave,
snip
The system described above relies on correct behavior of cookies on the Mac
in IE, and it works for us. I don't know if any behavior on the Tomcat side
has changed since 4.0.1, but I would tend to doubt it.
That's nice to hear :-|
Why are you using a secure cookie for the session
On 3/8/02 11:36 AM, Anders Rundgren [EMAIL PROTECTED] wrote:
2. Actually, we do absolutely nothing but request.getSession() which
triggers the session-mechanism according to my fellow developer. I.e.
we don't handle cookies ourselves, we rely on Tomcat's handling which
has worked fine until
12 matches
Mail list logo