On 7/23/07, Vincent Bray <[EMAIL PROTECTED]> wrote:
While I'm on a bit of a roll, I'll mention that subject that strikes
fear in to the hearts of intrepid geeks, mod_rewrite and its docs.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42898
The url in the PR is for 1.3 but trunk has the same issue.
What's the correct term for the bit of the request that RewriteRule's
first argument interogates (or mutilates, in many cases)? I think it's
"URI reference" but there's also "URL path" which is rather ambiguous.
The docs go on to demonstrate in detail what happens with examples,
but I think there could still be an improvement on the term.
(internally it's r->uri, right?)
Given (from trunk):
"Pattern is a perl compatible regular expression, which is applied to
the current URL. ``Current'' means the value of the URL when this rule
is applied. This may not be the originally requested URL, which may
already have matched a previous rule, and have been altered."
URL-path is the syntax I've tried to use elsewhere in the docs to
represent exactly this thing. See:
http://httpd.apache.org/docs/2.2/mod/directive-dict.html#Syntax
URI Reference is no more correct than URL in my opinion.
So I'd just replace URL with URL-path in the above paragraph.
You could also consider going down to the box labled "Note: Query
String" and changing the title to "What is matched?" and then change
the first sentence to "The Pattern will initially be matched against
the part of the URL after the hostname and port, and before the query
string. If you wish to match against the hostname, port, or query
string, use a RewriteCond with the %{HTTP_HOST}, %{SERVER_PORT}, or
%{QUERY_STRING} variables respectively." Then continue on with the
rest of the note as a new paragraph.
Joshua.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
