I decided to contact Dreamhost about my Apache logs showing 200 statuse codes for all mod_rewrite responses. It took seven back-and-forths to get across what was happening, discuss options, and conclude that “DreamHost systems are configured with a default environment meant to meet the most common webapp and customer requirements”.
status posts
Dreamhost, mod_rewrite, and logged status codes
I’ve done some more testing on the problem I mentioned before of all requests showing up as 200‘s in the Apache log on my Dreamhost shared server. I’m pretty sure it’s specific to their mod_rewrite module.
Struggling to figure out why every response from my Symfony application is showing up in the log files as a ‘200’ status. I thought it was related to this and this, since I’m running under FastCGI on Dreamhost, but attempting to set a Status header didn’t help. Setting a regular response header in a plain PHP file does work, in fact. If I use ‘mod_rewrite’ to write another URL to load that same plain file, however, the status shows as ‘200’, so it must have something to do with ‘mod_rewrite’. Must get to bed though, so I will have to try another day.