lucy24 - 8:23 pm on Oct 20, 2013 (gmt 0)
I suggest you work in the other direction. First get everything working correctly using htaccess. Then shift everything to the config file.
Is this a production server, or a pseudo-server like MAMP? Either way, make sure the config file is set for
Now you can change your htaccess every three minutes without having to restart the server. Also put in a set of lines something like this (exact wording may depend on Apache version)
ExpiresDefault "access plus 1 month"
ExpiresByType text/html "access"
Obviously you don't want this on your production server, unless you've got an entirely separate test site. But the intention is to keep your browser from caching anything, ever-- or even from asking whether the file has changed (the 304 response).
Another thing you can do in the config file is enable a RewriteLog. (For reasons I don't care to go into, you will have to get the wording from someone else. It should be in the Apache docs, though.) Most of it is incomprehensible, and no one LogLevel gives you the exact information you want and none of the information you don't want, but it will at least tell you whether mod_rewrite is looking at the request.