- From: Thomas Roessler <tlr@w3.org>
- Date: Sat, 12 Jan 2008 19:47:22 +0100
- To: Mark Nottingham <mnot@yahoo-inc.com>
- Cc: Brad Porter <bwporter@yahoo.com>, "WAF WG (public)" <public-appformats@w3.org>
On 2008-01-11 17:15:03 +1100, Mark Nottingham wrote: > That's the beauty of the server-side model; it works very well with caching. > > E.g., if the request is > > GET /foo HTTP/1.1 > Host: www.example.com > Referer-Root: http://other.example.org/ > > The response could be > > HTTP/1.1 200 OK > Cache-Control: max-age=3600 > Vary: Referer-Root > > ... > > which tells a cache that it can serve that response to other > clients, *as long as* they send the same Referer-Root header. The > cache ends up enforcing the server's policy on its behalf, > without any new software. If a 4xx response was seen before, the request would still go back to the original server, right? Thanks, -- Thomas Roessler, W3C <tlr@w3.org>
Received on Saturday, 12 January 2008 18:47:30 UTC