lucy24 - 7:54 pm on Apr 20, 2013 (gmt 0)
Huh. How did this post get missed for almost a month?
i'm not sure why you need the RewriteCond in that ruleset.
You need to make sure the rule isn't messing with the results of mod_dir activity. (Belt and suspenders: mod_dir normally executes after mod_rewrite, but you should protect yourself anyway.) You can achieve the same result with the [NS] flag. This flag works on SSIs and on both parts of mod_dir, but it doesn't work on the results of internal rewrites.
For a while I have been using a separate domain for final checking and I 403 everyone exept myself on the test domain.
Hm... OK... But really, a 500-class response would be more appropriate.
The conventional format for a domain-name-canonicalization condition is
meaning "exactly this form or exactly nothing". The "exactly nothing" is to allow for HTTP/1.0 requests. These are becoming rare for humans, but do still exist. I looked through my own logs recently, prompted by another thread, and found only proxies. But I think some exceedingly remote satellite-only areas are also 1.0.