https://issues.apache.org/bugzilla/show_bug.cgi?id=52171
Bug #: 52171
Summary: confusing documentation of request phases
Product: Apache httpd-2
Version: 2.3-HEAD
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
AssignedTo: docs@httpd.apache.org
ReportedBy: chea...@gmail.com
Classification: Unclassified
http://httpd.apache.org/docs/trunk/en/rewrite/tech.html#InternalAPI explains
the phases of a request to help understand how rewriting works. It contains:
In per-directory context (i.e., within .htaccess files and Directory blocks),
these rules are being applied after a URL has already been translated to a
filename. Because of this, mod_rewrite temporarily translates the filename back
into a URL, by stripping off directory path before appling the rules. (See the
RewriteBase directive to see how you can further manipulate how this is
handled.) Then, a new internal subrequest is issued with the new URL. This
restarts processing of the request phases. (Be careful to avoid rules that can
cause looping. See RewriteLooping for further discussion of this problem.
As we discussed on in #30021, this seems to say that some requests cause
subrequests. These subrequests would appear to also cause subrequests, which
would themselves cause subrequests, etc.
In other words, there is no explanation of what is different in the internal
subrequests which explains that processing a .htaccess does not cause infinite
recursion.
By the way, the last parenthesis is not closed.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-unsubscr...@httpd.apache.org
For additional commands, e-mail: docs-h...@httpd.apache.org
