Closed (fixed)
Project:
Bitcache
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
24 Nov 2008 at 16:28 UTC
Updated:
27 May 2017 at 13:41 UTC
Jump to comment: Most recent
Comments
Comment #1
miglius commentedMaybe a bitcache could adjust headers so that content pulled from the bitcache would get cached in the browser by default? The content is referenced by it's hash so it's not likely that it will change or expire :).
Comment #2
Arto commentedThose headers are not set by Bitcache, but rather by Drupal's core code. In release 6.x-1.0-alpha3 I've overridden the
Cache-Control,ExpiresandLast-Modifiedheaders set by Drupal; the relevant file isbitcache.server.inc(around line 126, in this release) and the relevant bits of the HTTP spec are:In this latest release, the Bitcache module outputs a
Cache-Controlheader of "private, no-transform" and anExpiresheader per 14.21 of the spec: "To mark a response as 'never expires,' an origin server sends an Expires date approximately one year from the time the response is sent."This can still be much improved upon, especially by implementing full support for conditional
ETagrequests (the SHA-1 checksums of bitstreams conveniently serve as strong entity tags), but it's already a far sight better than the previous headers that were preventing caching altogether.Suggestions and patches for further improvements would be most welcome.
Comment #4
jvieille commentedWorks great. I had to modify Boost for the same with this module
I added this function in boost.module
and added the call beside the existing boost_htaccess_cache_dir_put() in boost.module and boost.admin.inc