update: wrote the answer differently and more clearly
I have a solution which works without modifying the current HTTP protocol. I'd love to see an implementation of this.
Instead of telling the server our Etag we ASK the server about its Etag, and we compare it to the one we already have.
//Instead of saying "my etag is xyz",
//the client says: what is YOUR etag, server?"
HTTP conversation example with solution 1:
HTTP/1.1 200 OK
Date: Mon, 23 May 2005 22:38:34 GMT
Server: Apache/22.214.171.124 (Unix) (Red-Hat/Linux)
Last-Modified: Wed, 08 Jan 2003 23:11:55 GMT
Case 1, Client has an identical etag:
Connection closes, client loads page from cache.
Case 2, client has a mismatching etag:
GET...... //and a normal http conversation begins.
Edit: It is worth noting that there is a minor overhead, the server has to send the HTTP header twice: Once in response to the HEAD, and once in response to the GET. One theoretical workaround for this is modifying the HTTP protocol and adding a new method which requests header-less content. Then the client would request the HEAD only, and then the content only, if the etags mismatch.
Edit 2: I've followed makerofthings7's advice and posted this as a question on stackoverflow.