Slight clarification to the way rewrite works in per-directory context.
Suggested by Peter Kehl on the users mailing list.
Reviewed by: rbowen, covener, takashi
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@721621
13f79535-47bb-0310-9956-
ffa450edef68
correct Apache internal processing. Because the
per-directory rewriting comes late in the
process, the rewritten request
- has to be re-injected into the Apache kernel.
+ has to be re-injected into the Apache kernel, as if it
+ were a new request. (See <a href="../rewrite/rewrite_tech.html">mod_rewrite technical
+ details</a>.)
This is not the serious overhead it may seem to be -
this re-injection is completely internal to the
Apache server (and the same procedure is used by
correct Apache internal processing. Because the
per-directory rewriting comes late in the
process, the rewritten request
- has to be re-injected into the Apache kernel.
+ has to be re-injected into the Apache kernel, as if it
+ were a new request. (See <a
+ href="../rewrite/rewrite_tech.html">mod_rewrite technical
+ details</a>.)
This is not the serious overhead it may seem to be -
this re-injection is completely internal to the
Apache server (and the same procedure is used by