The last time I traced mod_rewrite on the front-end, and map files, discovered it opens, reads, and closes, the file *every single request*. I use a map like that to block IPs fast, but thought that was rather inefficient? should I not be concerned about such trifles?
-Justin RN> Brian Hirt writes: >> Once everything is running on the >> new mod perl, i shut down the original mod perl application. There is >> about 0.5 seconds of lag while the proxy reloads the rules. RN> We use proxies, but instead of modifying the proxy config, we use a RN> Rewrite rule of the form: RN> RewriteMap maps txt:/etc/httpd.maps RN> RewriteRule ^(.*) http://${maps:appserver}$1 [proxy] RN> When we release, we edit the /etc/httpd.maps file to point to a RN> different port or machine. RN> appserver foo.com:9999 RN> mod_rewrite rereads (or checks mtime of) the file on every request so RN> the change takes effect immediately. RN> Rob -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
