https://issues.apache.org/bugzilla/show_bug.cgi?id=30021
--- Comment #5 from Filipus Klutiero <[email protected]> 2011-10-10 17:04:08 UTC --- Thank you very much Rich. First, I now understand what API phases are about. The API in question seems to be an interface for modules. I wonder if this could be further clarified/simplified. Is "API phase" a very official name :-? Could this document simply refer to them as "Request processing phases" or something like that? Otherwise, there remains a part that I don't understand much: 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 API phases. "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.)" is particularly unclear to me. RewriteBase adds/restores to the beginning of the match, but this is phrased as if it controlled the stripping. I think something is missing explaining that the path is stripped, *and then "re-padded" to a URL*. Also, this says that processing of API phases restarts at the end. It is unclear what happens differently in the second processing. In other words, if processing restarts, there seems to be a loop, but the loop's exit condition is not obvious. -- 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: [email protected] For additional commands, e-mail: [email protected]
