There's a strong case not to use .htaccess on busy production boxes, since it requires unnecessary file I/O for every request made within that directory heirarchy (not only the index.php, but every favicon.ico, *.jpg, *.js, *.css, etc).
It's best to put your rewrite rules directly inside a virtualhost stanza. The only justifiable case for htaccess files is when you don't have access to httpd.conf, which is typical in shared hosting environments. -- Drew Kexiao Liao wrote: > My key point is, if we already enable mod_rewrite in the apache server, Can > we deploy Zend Framework Application without modifying httpd.conf file to > add alias name for the document_root directory? > > Kevin > > > Jack Sleight wrote: >> See the Graceful Restart section on this page: >> http://httpd.apache.org/docs/2.0/stopping.html >> Allows you to reconfigure Apache without completely restarting it. >> >> Kexiao Liao wrote: >>> When we finish Zend Framework application, and put it on the production >>> server. We need to modify the web server configuration file, in case of >>> Apache Server, we need to modify httpd.conf and add an alias name and the >>> associated <Directory> tag contents like following: >>> >>> <Directory "/pathto/zfgrid/document_root"> >>> Options all >>> AllowOverride all >>> Order allow,deny >>> Allow from all >>> </Directory> >>> >>> After modify the httpd.conf configuration file, we need restart Apache >>> server. For production site, this is not a good solution. >>> Is there another approach which we can avoid modification of httpd.conf >>> file >>> and restarting the server? >>> >>> >> -- >> Jack >> >> >
