When returning back to a page you have already visited & nothing has changed, Apache could return a 304 instead of a 200. This mean it would use the browser cache. I've tested this locally on my box and it appears to work with no issues. Feedback on this is would be appreciated. Etag is built from the files modification time and file size. If either one of these change then browser will request the full page.

Patch below

CommentFileSizeAuthor
#5 boost-etag-only.patch960 bytesmikeytown2
#4 boost-etag-only.patch1.13 KBmikeytown2
#3 boost-etag-only.patch928 bytesmikeytown2
#2 boost-etag-only.patch1.02 KBmikeytown2
boost-etag-only.patch1.49 KBmikeytown2

Comments

mikeytown2’s picture

mikeytown2 commented
Status: Active » Needs review
mikeytown2’s picture

mikeytown2 commented
StatusFileSize
new boost-etag-only.patch1.02 KB

Committed the bug fixes; here is just the experimental part

mikeytown2’s picture

mikeytown2 commented
StatusFileSize
new boost-etag-only.patch928 bytes

Only needed to comment out one line

mikeytown2’s picture

mikeytown2 commented
StatusFileSize
new boost-etag-only.patch1.13 KB

Let browser keep for 5 seconds; no need to ask again for 304. - eventually make this configurable... something to do with min cache lifetime; set the max to 15 minutes as setting this too high can be very dangerous, but having this set is very powerful in terms of sites speed. Ctrl-F5 will bypass this.
unset Last-Modified header.

mikeytown2’s picture

mikeytown2 commented
StatusFileSize
new boost-etag-only.patch960 bytes

and we are back to #3

mikeytown2’s picture

mikeytown2 commented
Status: Needs review » Reviewed & tested by the community

Reports have been good. Going to add this in soon.

bgm’s picture

bgm commented

Marked #982212: Cache-Control no-store, no-cache in Headers. Why? as a duplicate of this issue.

mgifford’s picture

mgifford
he/him
Primary language English
commented

There's a discussion going on about ETags in Core now #1573064: Remove unique ETag hack as it is no longer necessary

I'd think this is the defined best practice - http://developer.yahoo.com/performance/rules.html#etags

bgm’s picture

bgm commented
Status: Reviewed & tested by the community » Needs review

Interesting!

I think that in Boost we can rely on ETags generated by Apache, either from the filesystem inode, or the mtime (depending if in a cluster or not), since the cache is on the filesystem (unlike Drupal core).

If we rely on etags and do not impose "must-revalidate", we need to make sure that after a user login, the browser does not still serve pages from its cache, otherwise users have to reload each page after login.

Moving issue back to "needs review" since we should do more testing before committing this.