will trillich([EMAIL PROTECTED])@Sat, Apr 28, 2001 at 02:44:29PM -0500:
i've been tinkering with the modperl book examples
for Apache::Ticket*.pm (as described p305-322)...
it works for
linux/konqueror
linux/netscape
win/explorer
it doesn't work for
linux/lynx
- Original Message -
From: will trillich [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 28, 2001 9:44 PM
Subject: cookies work for some browsers, not for others... ?
[snip]
cf
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
HTMLHEAD
TITLE302 Found/TITLE
/HEADBODY
- Original Message -
From: will trillich [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, April 28, 2001 9:44 PM
Subject: cookies work for some browsers, not for others... ?
[snip]
cf
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
HTMLHEAD
TITLE302 Found/TITLE
/HEADBODY
i've been tinkering with the modperl book examples
for Apache::Ticket*.pm (as described p305-322)...
it works for
linux/konqueror
linux/netscape
win/explorer
it doesn't work for
linux/lynx
mac/netscape
the ones that do work get to the login page with two
in general, your problem with some browsers that otherwise support
cookies may be with issuing redirects and cookies on the same request,
which has been known to trip up some browsers. the easy workaround is
to use a meta refresh to do the redirection.
fmt: w70: No such file or directory
On Sat,
On Sat, Apr 28, 2001 at 12:54:17PM -0700, Jim Winstead wrote:
in general, your problem with some browsers that otherwise support
cookies may be with issuing redirects and cookies on the same request,
which has been known to trip up some browsers. the easy workaround is
to use a meta refresh
At 17:17 28/04/2001 -0500, will trillich wrote:
so i guess what you're saying is, some browsers look for
a redirect: header and then charge off to the new location
without handling any set-cookie: headers in the meantime?
Precisely. And some also don't report the cookie before the second page
On Sun, Apr 29, 2001 at 12:21:33AM +0200, Robin Berjon wrote:
At 17:17 28/04/2001 -0500, will trillich wrote:
so i guess what you're saying is, some browsers look for
a redirect: header and then charge off to the new location
without handling any set-cookie: headers in the meantime?
