Yes - it is the request over head - the client will still make the
request at which point the server has got to decide has it changed
before even - which for most static requests is the heaviest (slowest)
part before returning the not-changed response - and then serving the
content!
You are better to:
(a) set near future or mid future headers [ expires in a month or in a year]
(b) alter filenames if you significantly change the file contents [ we
use MD5 of content for js/css ]
Note this is "hyper-tuning" of Apache... some people may want to enable
it - it was originally set up when most users were on 28K/33.6K modems
(or slower) and the transfer of data was the slow part of the equation!
James
On 09/06/2015 13:27, Frederik Nosi wrote:
Hi James,
On 06/09/2015 10:24 AM, James Smith wrote:
From Apache point of view...
* Don't use .htaccess files... put everything in httpd.conf (or
equivalent) there is a huge file system performance hit {Apache
has to look for .htaccess files in the directory and any parent
directories}
include "AllowOverride None" in httpd.conf
* Remove etags (Header unset Etag/FileETag None)
Won't this disable conditional requests, ex. If-None-Match and
friends? Is your recomendation because of the header overhead or am I
missing something?
[...]
Thanks,
Frederik
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
