RE: PR 13211

[Frank Faubert <fr...@sane.com>]

Hello,

Does anyone have any additional ideas on how this can be fixed?

-Frank

-----Original Message-----
From: André Malo [mailto:nd@perlig.de] 
Sent: Wednesday, January 29, 2003 9:25 PM
To: dev@httpd.apache.org
Subject: Re: PR 13211


* Frank Faubert wrote:

> Add "CookieTracking on" to the end of the default httpd.conf file, start
up
> Apache and look at the headers for "/" -- only one cookie.  Now copy
> /tmp/apache/htdocs/index.html.en to /tmp/apache/htdocs/index.html and look
> at the headers for "/".  I get two cookies for every page that does NOT
use
> content negotiation (which unfortunately for me is my entire site...).

*hrm* I can verify that behaviour for directory requests (i.e. 
mod_dir/DirectoryIndex) without negotiation of the index file.

It seems to happen the following (GET / HTTP/1.0) without negotiation:

run_fixup:
->mod_usertrack: spot_cookie
->mod_dir: search and find index.html using sub_req_lookup_uri, which runs 
a fixup itself (->next spot_cookie)
  ->internal_fast_redirect -> apr_table_overlay(r->headers_out, 
                                                rr->headers_out)

                               ^^ two cookies here ^^

mod_negotiation instead (in case of index.html.var) does an additional 
normal internal_redirect to the negotiated resource, which drops the old 
stuff and cooks (not only) its own cookie.

right?

Conclusion: are overlay'ed tables in internal_fast_redirect semantically 
intended? Could someone please explain in slow words ;-), why?

> I also ran the same tests with v1.3.27 built as follows:
> And -never- got two cookies.

mod_dir uses a normal internal_redirect in 1.3.

nd
-- 
"Die Untergeschosse der Sempergalerie bleiben währenddessen aus
 statistischen Gründen geflutet." -- Spiegel Online