A more detailed analysis of what happens in Apache for this testcase is here: http://code.google.com/p/modpagespeed/issues/detail?id=234#c16
<http://code.google.com/p/modpagespeed/issues/detail?id=234#c16>The code says "internal_internal_redirect" but it makes a new request. I haven't had a chance to debug whether the pool would be a good place to attach our copy of the original uri. I'll check that out as well as r->main. Thanks for the suggestions. On Sat, Mar 12, 2011 at 10:02 PM, Eric Covener <cove...@gmail.com> wrote: > On Sat, Mar 12, 2011 at 9:45 PM, Ben Noordhuis <i...@bnoordhuis.nl> wrote: > > On Sun, Mar 13, 2011 at 02:48, Eric Covener <cove...@gmail.com> wrote: > >>> So I like #1 best. Any other opinions or ideas? > >> > >> I solved a similar problem recently by using apr_pool_userdata_set on > >> r->pool which you can still find after the internal redirects of > >> rewrite in htaccess / with PT flag. > > > > What Joshua is describing sounds like a sub-request and those get > > their own pool, without the user data of the parent pool. I would > > probably follow r->main. > > OP specifically mentions "internal redirect" and rewrite-in-htaccess. >
