Quickie: HTTP Caching in Practice

HTTP has been designed to improve application performances by providing support for response caching.
But with great power comes great responsibilities, and having efficient HTTP caching requires a clean URI design and a proper usage of HTTP request and response headers.

In this quickie session, you'll get an overview of how HTTP caching works and how you can take benefit of it to reduce the load on your Java applications.

Author:
Xavier Coulon
Xavier Coulon has been a Java developer for several years, and since he joined JBoss back in late 2011, he has been working on the OpenShift, JAX-RS and LiveReload components of JBoss Tools and JBoss Developer Studio. More recently, he also discovered the magic of Awestruct to write static websites with the freedom of lightweight markup languages.

[stokitko]

1. If-Match is never used for caching. It is intended for API usage
2. Last-Modified is a heavy header because uses formatted date. Use ETag instead in form "hex(MTime)-hex(Size)" the same as Nginx generates. If you are using load balancer you should check that all nodes generates the same ETag.
2. Pragma is old header, just not mention it. The same is for Expires. Use Cache-Control instead
3. 10:33 If-None-Match may have many ETags but you are expecting only one. This is fine but just know that this is not RFC complaint

[govindrai]

why wouldn't you make the video the entire size of the screen....