Comments on: Speed Tips: Remove Last-Modified Header

By: Matt

Matt — Mon, 02 Feb 2009 00:13:55 +0000

I love this tip. I’ve done a lot of optimization research and actually nobody ever suggested to remove the Last-Modified header and it’s interesting to know that the browser will not pass in those “If-” requests which is once again less bytes that have to travel across the web.

My only question is why are you suggesting NOT to remove the Last-Modified header for .html files?

By: Robot Terror

Robot Terror — Tue, 29 Apr 2008 19:41:40 +0000

This is what I currently have in my .htaccess file at the root. Do you see any problems with what I have here?

First off, once your rules are correct be sure to move the rules out of .htaccess and into the httpd.conf file for the Directory section of your DocumentRoot. Why? .htaccess is inherently slow as it must be read for each and every request that starts in or goes deeper than the directory in which it resides (and for which AllowOverride is enabled). See the Apache documentation for .htaccess files for more information

By: Spencer

Spencer — Tue, 29 Apr 2008 04:36:25 +0000

This is what I currently have in my .htaccess file at the root. Do you see any problems with what I have here? Would you organize it differently? I don't know much about .htaccess files, but would love to see if this is ok for my server. Here it is below...

FileETag None
Header unset ETag
Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate"
Header set Pragma "no-cache"
Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"
 
Header unset ETag
FileETag None
 
SetOutputFilter DEFLATE
 
Header set Expires "Thu, 15 Apr 2010 20:00:00 GMT"
 
Header unset Last-Modified

Thanks for your help!

By: Robot Terror

Robot Terror — Mon, 03 Dec 2007 04:07:08 +0000

BTW…auto-playing music is a good way to lose traffic. Is this a MySpace page?

By: Robot Terror

Robot Terror — Mon, 03 Dec 2007 04:06:14 +0000

Yes, this will speed individual requests, but for those sites with actual traffic they may crawl to a halt due to re-requested content from frequent visitors (think RSS feeds) and spiderbots (Google, etc.). It’s a trade-off that massive scalable systems must consider: slow each request a little to be able to serve all requests reasonably fast.