{"id":44154,"date":"2015-09-24T10:00:54","date_gmt":"2015-09-24T07:00:54","guid":{"rendered":"http:\/\/www.javacodegeeks.com\/?p=44154"},"modified":"2015-09-22T22:09:51","modified_gmt":"2015-09-22T19:09:51","slug":"resource-versioning-with-spring-mvc","status":"publish","type":"post","link":"https:\/\/www.javacodegeeks.com\/2015\/09\/resource-versioning-with-spring-mvc.html","title":{"rendered":"Resource versioning with Spring MVC"},"content":{"rendered":"

When serving static resources, it is common practice to append some kind of version information to the resource URL. This allows the browser to cache resources for an unlimited time. Whenever the content of the resource is changed, the version information in the URL is changed too. The updated URL forces the client browser to discard the cached resource and reload the latest resource version from the server.<\/p>\n

With Spring it only takes two simple steps to configure versioned resource URLs. In this post we will see how it works.<\/p>\n

Serving versioned URLs<\/h2>\n

First we need to tell Spring that resources should be accessible via a versioned URL. This is done in the resource handler MVC configuration:<\/p>\n

@Configuration\r\npublic\u00a0class\u00a0MvcApplication\u00a0extends\u00a0WebMvcConfigurerAdapter\u00a0{\r\n\r\n\u00a0\u00a0@Override\r\n\u00a0\u00a0public\u00a0void\u00a0addResourceHandlers(ResourceHandlerRegistry\u00a0registry)\u00a0{\r\n\u00a0\u00a0\u00a0\u00a0VersionResourceResolver\u00a0versionResourceResolver\u00a0=\u00a0new\u00a0VersionResourceResolver()\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0.addVersionStrategy(new\u00a0ContentVersionStrategy(),\u00a0\"\/**\");\r\n\r\n\u00a0\u00a0\u00a0\u00a0registry.addResourceHandler(\"\/javascript\/*.js\")\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0.addResourceLocations(\"classpath:\/static\/\")\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0.setCachePeriod(60\u00a0*\u00a060\u00a0*\u00a024\u00a0*\u00a0365)\u00a0\/*\u00a0one\u00a0year\u00a0*\/\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0.resourceChain(true)\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0.addResolver(versionResourceResolver);\r\n\u00a0\u00a0}\r\n\r\n\u00a0\u00a0...\r\n}<\/pre>\n
Here we create a resource handler for JavaScript files located in folder named static inside the classpath. The cache period for these JavaScript files is set to one year. The important part is the VersionResourceResolver<\/a> which supports resource URLs with version information. A VersionStrategy<\/a> is used to obtain the actual version for a resource.<\/p>\n
In this example we use a ContentVersionStrategy<\/a>. This VersionStrategy implementation calculates an MD5 hash from the content of the resource and appends it to the file name.
 
<\/div> <\/div><\/p>\n
For example: Assume we have a JavaScript file test.js inside the classpath:\/static\/ directory. The MD5 hash for test.js is 69ea0cf3b5941340f06ea65583193168.<\/p>\n
We can now send a request to:<\/p>\n
\/javascript\/test-69ea0cf3b5941340f06ea65583193168.js<\/pre>\n
which will resolve to classpath:\/static\/test.js.<\/p>\n
Note that it is still possible to request the resource without the MD5 hash. So this request works too:<\/p>\n
\/javascript\/test.js<\/pre>\n
An alternative VersionStrategy implementation is FixedVersionStrategy<\/a>. FixedVersionStrategy uses a fixed version string that added as prefix to the resource path.<\/p>\n
For example:<\/p>\n
\/v1.2.3\/javascript\/test.js<\/pre>\n
Generating versioned URLs<\/h2>\n
Now we need to make sure the application generates resource URLs that contain the MD5 hash.<\/p>\n
One approach for this is to use a ResourceUrlProvider<\/a>. With a ResourceUrlProvider a resource URL (e.g. \/javascript\/test.js) can be converted to a versioned URL (e.g. \/javascript\/test-69ea0cf3b5941340f06ea65583193168.js). A ResourceUrlProvider bean with the id mvcResourceUrlProvider is automatically declared with the MVC configuration.<\/p>\n
In case you are using Thymeleaf as template engine, you can access the ResourceUrlProvider bean directly from templates using the @bean syntax.<\/p>\n
For example:<\/p>\n
<script\u00a0type=\"application\/javascript\"\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0th:src=\"${@mvcResourceUrlProvider.getForLookupPath('\/javascript\/test.js')}\">\r\n<\/script><\/pre>\n
If you are using a template engine which does not give you direct access to Spring beans, you can add the ResourceUrlProvider bean to the model attributes. Using a ControllerAdvice<\/a>, this might look like this:<\/p>\n
@ControllerAdvice\r\npublic\u00a0class\u00a0ResourceUrlAdvice\u00a0{\r\n\r\n\u00a0\u00a0@Inject\r\n\u00a0\u00a0ResourceUrlProvider\u00a0resourceUrlProvider;\r\n\r\n\u00a0\u00a0@ModelAttribute(\"urls\")\r\n\u00a0\u00a0public\u00a0ResourceUrlProvider\u00a0urls()\u00a0{\r\n\u00a0\u00a0\u00a0\u00a0return\u00a0this.resourceUrlProvider;\r\n\u00a0\u00a0}\r\n}<\/pre>\n
Inside the view we can then access the ResourceUrlProvider using the urls model attribute:<\/p>\n
<script\u00a0type=\"application\/javascript\"\u00a0\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0th:src=\"${urls.getForLookupPath('\/javascript\/test.js')}\">\r\n<\/script><\/pre>\n
This approach should work with all template engines that support method calls.<\/p>\n
An alternative approach to generate versioned URLs is the use of ResourceUrlEncodingFilter<\/a>. This is a Servlet Filter that overrides the HttpServletResponse.encodeURL() method to generate versioned resource URLs.<\/p>\n
To make use of the ResourceUrlEncodingFilter we simply have to add an additional bean to our configuration class:<\/p>\n
@SpringBootApplication\r\npublic\u00a0class\u00a0MvcApplication\u00a0extends\u00a0WebMvcConfigurerAdapter\u00a0{\r\n\r\n\u00a0\u00a0@Override\r\n\u00a0\u00a0public\u00a0void\u00a0addResourceHandlers(ResourceHandlerRegistry\u00a0registry)\u00a0{\r\n\u00a0\u00a0\u00a0\u00a0\/\/\u00a0same\u00a0as\u00a0before\u00a0..\r\n\u00a0\u00a0}\r\n\r\n\u00a0\u00a0@Bean\r\n\u00a0\u00a0public\u00a0ResourceUrlEncodingFilter\u00a0resourceUrlEncodingFilter()\u00a0{\r\n\u00a0\u00a0\u00a0\u00a0return\u00a0new\u00a0ResourceUrlEncodingFilter();\r\n\u00a0\u00a0}\r\n\r\n\u00a0\u00a0...\r\n}<\/pre>\n
If the template engine you are using calls the response encodeURL() method, the version information will be automatically added to the URL. This will work in JSPs, Thymeleaf, FreeMarker and Velocity.<\/p>\n
For example: With Thymeleaf we can use the standard @{..} syntax to create URLs:<\/p>\n
<script\u00a0type=\"application\/javascript\"\u00a0th:src=\"@{\/javascript\/test.js}\"><\/script><\/pre>\n
This will result in:<\/p>\n
<script\u00a0type=\"application\/javascript\"\u00a0\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0src=\"\/javascript\/test-69ea0cf3b5941340f06ea65583193168.js\">\r\n<\/script><\/pre>\n
Summary<\/h2>\n
Adding version information to resource URLs is a common practice to maximize browser caching. With Spring we just have to define a VersionResourceResolver and a VersionStrategy to serve versioned URLs. The easiest way to generate versioned URLs inside template engines, is the use of an ResourceUrlEncodingFilter.<\/p>\n
If the standard VersionStrategy implementations do not match your requirements, you can create our own VersionStrategy implementation.<\/p>\n