* William A. Rowe, Jr. wrote:
> At 08:10 AM 2/28/2003, Andr� 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 request.
>>Can someone explain, why? Why not using only the new header table? It bites
>>us, for example, with cookies, which are set twice (mod_usertrack).
>
> Good question. It's a bit historical. Some of the headers are connection
> 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.
>
> It would be nice if we set up connection-oriented stuff at the start of the request
> in it's own table, duplicated that table for the request, and if a request 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
assignment in fast_redirect. What about this option? (and who can define
them? ;-)
nd
--
>kann mir jemand sagen, was genau @-Domains sind?
Ein Mythos. Ein Werbetrick. Verarsche. Nenn es wie du willst...
-- Alexandra Buss und Bj�rn H�hrmann in dciwam
