views:

3150

answers:

5

I have pushed my .htaccess files to the production severs, but they don't work. Would a restart be the next step, or should I check something else.

+19  A: 

No.

Milen A. Radev
A: 

What's in your .htaccess? RewriteRules? Check that mod_rewrite is installed and enabled.

Other stuff? Try setting AllowOverride to 'all' on that directory.

ceejayoz
A: 

only if you have NOT added the mod re-write module to apache.

you only need to restart apache if you change any apache ".conf" files

ethyreal
+7  A: 

From the apache documentation: Most commonly, the problem is that AllowOverride is not set such that your configuration directives are being honored. Make sure that you don't have a AllowOverride None in effect for the file scope in question. A good test for this is to put garbage in your .htaccess file and reload. If a server error is not generated, then you almost certainly have AllowOverride None in effect.

PiedPiper
Dropping link to Apache - AllowOverride:http://httpd.apache.org/docs/2.2/mod/core.html#AllowOverride
scunliffe
I add this line "<directory / ></directory>" to my .htaccess to generate an error in the log. It will say "<Directory not allowed here" and I know it's reading my file.
Mnebuerquo
+2  A: 

A restart is not required for changes to .htaccess. Something else is wrong.

Make sure your .htaccess includes the statement

RewriteEngine on

which is required even if it's also present in httpd.conf. Also check that .htaccess is readable by the httpd process.
Check the error_log - it will tell you of any errors in .htaccess if it's being used. Putting an intentional syntax error in .htaccess is a good check to make sure the file is being used -- you should get a 500 error on any page in the same directory.

Lastly, you can enable a rewrite log using commands like the following in your httpd.conf:

RewriteLog "logs/rewritelog"

RewriteLogLevel 7

The log file thus generated will give you the gory detail of which rewrite rules matched and how they were handled.

TomG