Not exactly. The value of THE_REQUEST will look something like this:
GET /index.html HTTP/1.1
The initial letter-matching pattern is meant to match the HTTP method (GET, POST, HEAD, etc.), followed by a space. Once we get into the request path, then the condition matches on .*.
This code removed index.html at the end of a URL, so that when people request example.com/index.hml they are 301 redirected to example.com/
The reason people use THE_REQUEST for this, is because that’s the only way you can effectively remove the DirectoryIndex to another place, since the requested URI as far as Apache is concerned is index.html when you request /, leading to an infinite loop of redirects.
THE_REQUEST shows you the raw headers of the request, i.e., the URL people requested, instead of the URL apache inferred people were requesting.
Sure feel free http://www.webmasterworld.com/apache/4562115.htm I hate to pit your two minds against each other but my need to get to the bottom of this is greater. I wish I could participate in the discussion. But I’m afraid I will never fully get this stuff. I’m guessing you already jumped in?
Right, I was confusing index.html via mod_dir with index.php served via RewriteRule (“catch-all”); in the latter case you DO need to use THE_REQUEST if you want to redirect away from index.php.
But indeed, in the case of index.html I have no idea why one would use THE_REQUEST.
“” It’s unusual to meet such a vigorous defense of inefficient rules and careless coding. Can’t help but wonder if there’s a backstory we’re not getting. “”
I’ll come clean over there. But I do not feel bad because they refused to answer my original question I proposed to you with 3 weeks ago about auto non redirects to addon domains. And they refused to answer I suspect because there is no answer using their preferred method of thinking.