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 there is some other way - like faking that the file-date has changed.
(i am not quite confortable with patching every new apache version again,
or would it be a good idea to send this to the apache-guys ?)
Thanks again,
Nenad
Andrew Gilmartin wrote:
>
> > > How can I force Apache to send the Set-Cookie header even if the
> > > document being delivered has not changed? I suspect that I am not
> the
> > > first person to run into this problem. A search of the list was
> > > unsuccessful, unfortunately.
> >
> > i've not tested, but it looks like Set-Cookie is left out on purpose
> > (maybe an http rfc compliance thing or just a bug), this patch might
> > help..
> >
> > --- src/main/http_protocol.c~ Tue Apr 17 11:30:14 2001
> > +++ src/main/http_protocol.c Tue Jun 19 09:46:29 2001
> > @@ -2637,6 +2637,7 @@
> > "Warning",
> > "WWW-Authenticate",
> > "Proxy-Authenticate",
> > + "Set-Cookie",
> > NULL);
> >
> > terminate_header(r->connection->client);
>
> I tested it and it works. Thank you for such a quick and authoritative
> answer.
>
> -- Andrew
>
> ---
> Andrew Gilmartin
> Ingenta / Dynamic Diagrams
> [EMAIL PROTECTED]
