Ben,
I don't know of any way of checking (someone correct me if I'm wrong!).
What I have done is to attach an attribute to the session, redirect to a
small .jsp page with a div visibility: hidden; tag surronding a form
that automatically submits back to the servlet. The servlet can then
check
hi,
this begs the question, is it bad practice to require users to enable
cookies?
--- Mike Fowler [EMAIL PROTECTED] wrote:
Ben,
I don't know of any way of checking (someone correct me if I'm
wrong!).
What I have done is to attach an attribute to the session, redirect
to a
small .jsp
-Original Message-
From: Woodchuck [mailto:[EMAIL PROTECTED]
Sent: Friday, June 25, 2004 9:29 AM
To: Tomcat Users List
Subject: Re: Determination if a client has sessions enabled or not.
hi,
this begs the question, is it bad practice to require users to enable
cookies
I tend to agree and would advocate the use of URL encoding for all
stateful web-apps. However they have the drawback of making your URL
look something like:
http://localhost:8080/manager/html/list;jsessionid=C76172F9BD3E29A9AFDEBDA349F853DF
So you use cookies for tidy URLs.
-Mike Fowler
I could
if a client has sessions enabled or not.
hi,
this begs the question, is it bad practice to require users to
enable
cookies?
--- Mike Fowler [EMAIL PROTECTED] wrote:
Ben,
I don't know of any way of checking (someone correct me if I'm
wrong!).
What I have done
I think it's a good idea to try as much as possible to cater to
cookieless users, differing browsers and so on as this allows you to
create a single web-app that will function and look the same across a
multitude of browsers.
As a Mozilla user I come across site after site that takes advantage
: Woodchuck [mailto:[EMAIL PROTECTED]
Sent: Friday, June 25, 2004 10:16 AM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: RE: Determination if a client has sessions enabled or not.
it used to be more common to have warnings on websites that say cookies
are required. nowadays, these warnings
