Speed Up Sites with htaccess Caching

produke writes "Increase your page load times and save bandwidth with easy and really effective methods using apache htaccess directives. mod_headers to set expires, and max-age, and cache-control headers on certain filetypes. The second method employs mod_expires to do the same thing -- together with FileETag, makes for some very fast page loads!"

Comments

caching htaccess?

[oneiros27]

Here I was, thinking that someone had a solution for the slowdown caused by using htaccess files in the first place.

They don't.

If you're going to set caching in your server to decrease load time, make sure to set in the main configuation files, and disable htaccess, which can potentially increase the time of every page load. (the decreased hits and bandwidth may be an advantage to you -- you'll have to benchmark to see if this solution helps or hurts you for your given platform and usage patterns)

httpd.conf

[Nos.]

Its in the comments on that site, but remember, you're always better off putting this kind of stuff in your httpd.conf as opposed to .htaccess files. htaccess files reduce performance on your webserver.

Re:httpd.conf

[bcat24]

Unless you're on a shared hosting plan. Then you kind of need to go with .htaccess.

So using cache control headers is "news", huh?

[xxxJonBoyxxx]

So using cache control headers is "news", huh?

Also, from the comment on this "innovative" article:

1.DrBacchus said:
Yes, these techniques *can* result in performance improvements, but should be put in your main server configuration file, rather than in .htaccess files. .htaccess files, by their very nature, cause performance degradation on your website, and so should be avoided whenever possible.

Re:So using cache control headers is "news", huh?

[Trogre]

I'm interested in this. Can you please elaborate and point me to the relevant discussion or, even better, a patch?

htaccess performance loss

[oneiros27]

If you're on a shared hosting site, and htaccess is already turned on, you're already affected.

Basically, if someone were to request a file from your site: /this/is/some/deep/file

Then apache has to look for, and if there, parse, each of the following files: /.htaccess /this/.htaccess /this/is/.htaccess /this/is/some/.htaccess /this/is/some/deep/.htaccess

And then, should the rules allow the file to be served, it'll be sent to the requestor.

So the problem isn't the .htaccess file itself (unless you have a whole bunch of unnecessary rules, increasing the size of the file), but just turning on support for .htaccess files. I think the parsing of the .htaccess files is cached, but the system still has to check for the files each time, and see if they've changed.

As for question about redirects -- you have to tell the system how to process the 404s ... I've seen lots of implementations, including setting a template system to resolve all 404s, and then using the path requested to drive a template system ... which of course meant that _every_ page on the site was served as a 404. (I was given the task of trying to figure out what the person had done, as they had tried upgrading the site, and wanted to archive the old site, and it took me much longer than expected to figure out what the horrible hack was that they used. (and of course, no services had cached the site, so I could see what it used to look like, because it always served 404s)) ... unless you have some way of specifying a handler for 404 errors without .htaccess (which you don't, as you've mentioned it's shared hosting), the question about .htaccess makes no sense.... it's still getting called, and you're still taking the performance hit, no matter what you pass off to.