Talk:Rewrite engine
From Wikipedia, the free encyclopedia
A few days of research and much frustration seems to prove the following behaviors of mod_rewrite in Apache 1.3
Oldfilename is compared against regex patterns and condition criteria. If matched, rewrite rebuilds a newfilename by Substitution, then exits if [L] flag exists. If oldfilename != newfilename, the API process is started over. This eventually leads the newfilename back to the htaccess for matching.
Newfilename won't leave this 'loop' until: no regex matches are found, a matching rewrite has a [L] flag but doesn't change the filename, or the filename matches the same rewrite rule that changed it on the last loop. This last behavior is probably so an endless loop doesn't occur by default.
Also a regex backreference throws a 500 error if the referenced tag is optional and doesn't occur. (with a ? or * quantifier)
[edit] examples?
Using a URL rewrite engine, the website software can be presented with URLs in one form, while actual requests (and URLs seen by the user) are in another form. So rewrite engines allow URLs to be tidied up and made more user friendly, by configuring rewrite rules, rather than modifying the webserver softwar
Sorry but i don't understand, more user friendly?, can someone supply an example what url rewriting actually does?
jf: I second this original request. This page was helpful, but we need 3-4 examples of different uses of URL rewriting. That would do the trick.
