search

ericwang14 / webutilities

Automatically exported from code.google.com/p/webutilities
0 stars 0 forks source link

Support ETag and handle If-None-Match and If-Modified-Since request headers #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
With the expires/cache-control header, browser will cache the resources locally 
and will not make a server request. Meantime if resources is modified on 
server, server somehow needs to tell the clients/browsers to expire their local 
cache and fetch new ones.

This is mostly done through URL change - either versioning or hash coding. We 
need to take care of this as well.

Original issue reported on code.google.com by rr.patil...@gmail.com on 5 Apr 2011 at 11:05

GoogleCodeExporter commented 9 years ago 
This is good article by Brandon Carlson - 
http://blog.bcarlso.net/2007/10/19/tomcat-weak-etags-and-javascript-css-caching

May be we can use Strong ETag of our own in JSCSSMergeServlet.

Original comment by rr.patil...@gmail.com on 5 Apr 2011 at 11:46

GoogleCodeExporter commented 9 years ago 
This Joe Gregorio's article is good too - 
http://bitworking.org/news/150/REST-Tip-Deep-etags-give-you-more-benefits

Original comment by rr.patil...@gmail.com on 5 Apr 2011 at 11:48

GoogleCodeExporter commented 9 years ago 
To make the client side caching effective yet letting the client know when 
resource changes, support ETag and handle If-None-Match and If-Modified-Since 
headers. Respond 304 (or 200) as appropriate.

Original comment by rr.patil...@gmail.com on 7 Apr 2011 at 6:40

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/webutilities/source/detail?r=219
http://code.google.com/p/webutilities/source/detail?r=220

Original comment by rr.patil...@gmail.com on 14 Apr 2011 at 3:50