On 21 Jun 2001, Randal L. Schwartz wrote:
Uh, it seems a bit fishy to me. nothing's changed, but by the way,
set this cookie please. Why change a cookie if nothing else has
changed?
don't gimme this 'fishy' mumbo jumbo, i'm willing to accept a valid reason
why set-cookie shouldn't be
Hello,
DMi'm willing to accept a valid reason why set-cookie shouldn't be
DMincluded in a 304 response, but i have yet to hear one.
For the record, I agree, and I agree that mod_perl should allow this.
From a practical point of view, though, I've tended to avoid this
situation altogether in
On Wed, 20 Jun 2001, Nenad Steric wrote:
Hi,
Thanks for your answer, saved me days of probably fruitless fidling around with
modperl.
Your solution solved my problems (see Sending Cookies on Page-Reload)
the question remains if this violates some RFC's (or breaks some browsers),
and if
On Mon, 18 Jun 2001, Andrew Gilmartin wrote:
I have PerlAuthenHandler handler that sets a cookie on authentication
success. The cookie records, in part, the time of the last access to
the site. Therefore for each access the cookie is updated. When a new
document is accessed or a CGI script
