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." Do we: [ ] Change URL to "URI reference" [ ] Explain parenthetically (yay!) like: .. which is applied to the current URL (the part after the host name/port and not including the query string). [ ] Add another paragraph, like: The <code>Pattern</code> refers to the part of the URL after the host name/port and doesn't include any query string. E.g. for http://www.example.com:80/foo/bar.html?quux=wibble the <code>Pattern</code> is initially /foo/bar.html. .. but then that needs an explaination of differences between per-server and per-directory, like http://wiki.apache.org/httpd/RewriteContext [ ] Mark the bug as invalid given the examples already provided. Opinions, please. -- noodl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
