I spent numerous hours looking into what appear now to be separate gzipping issues / non-issues with my site.
Continue reading post "#1724"apache posts page 2
Not sure if it was a recent Mac security update or a change with macports, but my local apache server broke and is requiring quite a bit of work to get it functional again.
Dreamhost 200 status log conclusion
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”.
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.
On my site, I’m using Apache’s ‘mod_deflate’ and ‘mod_filter’ to compress my compressible responses (mostly text), with a setup based on h5bp’s server config. I got my sites running over HTTPS recently, and today, when looking at my site performance with webpagetest.org, I noticed that my content wasn’t compressing. It was still working fine over HTTP. I noticed in h5bp’s comments that <IfModule mod_filter.c> could be removed in Apache versions below 2.3.x. I removed it, and sure enough, compression was working again. I’m not sure why it’s different depending on what protocol I use. Perhaps Dreamhost has separate versions of Apache running for the two protocols. Or perhaps it’s just something different about the configuration in the virtual hosts. Regardless, it’s working now. I just hope this doesn’t cause problems whenever they move to Apache 2.4.