Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
From: =?ISO-8859-1?Q?Andr=E9?= Malo <nd@perlig.de>
Subject: Re: internal_fast_redirect question
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Organization: TIMTOWTDI
References: <n2m-g.brvnvwo586gwndparker@news.perlig.de>
 <5.2.0.9.2.20030228124651.02886c80@pop3.rowe-clan.net>
Date: Fri, 28 Feb 2003 22:30:06 +0100
To: dev@httpd.apache.org
Message-ID: <n2m-g.fl2wuh80bnp5$ndparker@news.perlig.de>
User-Agent: Yes!

* William A. Rowe, Jr. wrote:

> At 08:10 AM 2/28/2003, Andr=E9 Malo wrote:
>>In contrast to a "normal" internal redirect the fast variant does an
>>apr_table_overlay of the header tables of the original and the new reques=
t.
>>Can someone explain, why? Why not using only the new header table? It bit=
es
>>us, for example, with cookies, which are set twice (mod_usertrack).
>=20
> Good question.  It's a bit historical.  Some of the headers are connectio=
n
> related, and fast internal redirect doesn't do all of the connection work=
 that
> the full redirect would.  I'd need to step the code paths, but in the end=
, these
> two flavors should not differ so much.
>=20
> It would be nice if we set up connection-oriented stuff at the start of t=
he request
> in it's own table, duplicated that table for the request, and if a reques=
t does any
> sort of redirect, simply grab a fresh connection table.

If we are able to exactly define these headers, we can simply filter the=20
assignment in fast_redirect. What about this option? (and who can define=20
them? ;-)

nd
--=20
>kann mir jemand sagen, was genau @-Domains sind?
Ein Mythos. Ein Werbetrick. Verarsche. Nenn es wie du willst...

                 -- Alexandra Buss und Bj=F6rn H=F6hrmann in dciwam