News for hackers. Stuff that matters.

A comment on Caching the uncacheable: CloudFlare's Railgun. Parent comment

Re:Caching the uncacheable: CloudFlare's Railgun by judofyr on Monday July 02, 2012 @04:33AM (#4187944)
> It seems as though folk are starting to see that in most environments caching ought to be driven by POSTs, not GETs + timeouts.

HTTP supports that too (through ETag and 204 Not Modified).

[ Parent | on HN ]
Re:Caching the uncacheable: CloudFlare's Railgun by jacques_chester on Monday July 02, 2012 @04:54AM (#4188011)
I meant in terms of server-side caching.
[ Parent | on HN ]
Re:Caching the uncacheable: CloudFlare's Railgun by jddil on Monday July 02, 2012 @11:35PM (#4192378)
204 is no content. Think you meant 304.
[ Parent | on HN ]