1. Overview
This tutorial will explore how to serve static resources with Spring using both XML and Java configuration.
2. Using Spring Boot
Spring Boot comes with a pre-configured implementation of ResourceHttpRequestHandler to facilitate serving static resources.
By default, this handler serves static content from any of the /static, /public, /resources, and /META-INF/resources directories that are on the classpath. Since src/main/resources is typically on the classpath by default, we can place any of these directories there.
For example, if we put an about.html file inside the /static directory in our classpath, then we can access that file via http://localhost:8080/about.html. Similarly, we can achieve the same result by adding that file in the other mentioned directories.
2.1. Custom Path Patterns
By default, Spring Boot serves all static content under the root part of the request, /**. Even though it seems to be a good default configuration, we can change it via the spring.mvc.static-path-pattern configuration property.
For example, if we want to access the same file via http://localhost:8080/content/about.html, we can say so in our application.properties:
spring.mvc.static-path-pattern=/content/**
In WebFlux environments, we should use the spring.webflux.static-path-pattern property.
2.2. Custom Directories
Similar to path patterns, it’s also possible to change the default resource locations via the spring.web.resources.static-locations configuration property. This property can accept multiple comma-separated resource locations:
spring.web.resources.static-locations=classpath:/files/,classpath:/static-files
Here we’re serving static contents from the /files and /static-files directories inside the classpath. Moreover, Spring Boot can serve static files from outside of the classpath:
spring.web.resources.static-locations=file:/opt/files
Here we’re using the file resource signature, file:/, to serve files from our local disk.
3. XML Configuration
If we need to go the old fashion way with XML-based configuration, we can make good use of the mvc:resources element to point to the location of resources with a specific public URL pattern.
For example, the following line will serve all requests for resources coming in with a public URL pattern, like “*/resources/**”,* by searching in the “/*resources/*” directory under the root folder in our application:
<mvc:resources mapping="/resources/**" location="/resources/" />
Now we can access a CSS file like in the following HTML page:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<html>
<head>
<link href="<c:url value="/resources/myCss.css" />" rel="stylesheet">
<title>Home</title>
</head>
<body>
<h1>Hello world!</h1>
</body>
</html>
4. The ResourceHttpRequestHandler
Spring 3.1. introduced the ResourceHand**lerRegistry to configure ResourceHttpRequestHandlers for serving static resources from the classpath, the WAR, or the file system. We can configure the ResourceHandlerRegistry programmatically inside our web context configuration class.
4.1. Serving a Resource Stored in the WAR
To illustrate this, we’ll use the same URL as before to point to myCss.css, but now the actual file will be located in the WAR’s webapp/resources folder, which is where we should place static resources when deploying Spring 3.1+ applications:
@Configuration
@EnableWebMvc
public class MvcConfig implements WebMvcConfigurer {
@Override
public void addResourceHandlers(ResourceHandlerRegistry registry) {
registry
.addResourceHandler("/resources/**")
.addResourceLocations("/resources/");
}
}
Let’s analyze this example a bit. First, we configure the external-facing URI path by defining a resource handler. Then we map that external-facing URI path internally to the physical path where the resources are actually located.
We can, of course, define multiple resource handlers using this simple, yet flexible, API.
Now the following line in an html page would get us the myCss.css resource inside the webapp/resources directory:
<link href="<c:url value="/resources/myCss.css" />" rel="stylesheet">
4.2. Serving a Resource Stored in the File System
Let’s say we want to serve a resource stored in the /opt/files/ directory whenever a request comes in for the public URL matching the /files/** pattern. We simply configure the URL pattern and map it to that particular location on the disk:
@Override
public void addResourceHandlers(ResourceHandlerRegistry registry) {
registry
.addResourceHandler("/files/**")
.addResourceLocations("file:/opt/files/");
}
For Windows users, the argument passed to addResourceLocations for this example would be “*file:///C:/opt/files/*“.
Once we configure the resource location, we can use the mapped URL pattern in our home.html to load an image stored in the file system:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<html>
<head>
<link href="<c:url value="/resources/myCss.css" />" rel="stylesheet">
<title>Home</title>
</head>
<body>
<h1>Hello world!</h1>
<img alt="image" src="<c:url value="files/myImage.png" />">
</body>
</html>
4.3. Configuring Multiple Locations for a Resource
What if we want to look for a resource in more than one location?
We can include multiple locations with the addResourceLocations method. The list of locations will be searched in order until the resource is found:
@Override
public void addResourceHandlers(ResourceHandlerRegistry registry) {
registry
.addResourceHandler("/resources/**")
.addResourceLocations("/resources/","classpath:/other-resources/");
}
The following curl request will display the Hello.html page stored in either the application’s webappp/resources or the other-resources folder in the classpath:
curl -i http://localhost:8080/handling-spring-static-resources/resources/Hello.html
5. The New ResourceResolvers
Spring 4.1. provides, with the new ResourcesResolvers, different types of resource resolvers that can be used to optimize browser performance when loading static resources. These resolvers can be chained and cached in the browser to optimize request handling.
5.1. The PathResourceResolver
This is the simplest resolver, and its purpose is to find a resource given a public URL pattern. In fact, if we don’t add a ResourceResolver to the ResourceChainRegistration, this is the default resolver.
Let’s look at an example:
@Override
public void addResourceHandlers(ResourceHandlerRegistry registry) {
registry
.addResourceHandler("/resources/**")
.addResourceLocations("/resources/","/other-resources/")
.setCachePeriod(3600)
.resourceChain(true)
.addResolver(new PathResourceResolver());
}
Things to notice:
- We’re registering the PathResourceResolver in the resource chain as the sole ResourceResolver in it. We can refer to section 4.3. to see how to chain more than one ResourceResolver.
- The resources served will be cached in the browser for 3600 seconds.
- The chain is finally configured with the method resourceChain(true).
Now for the HTML code that, in conjunction with the PathResourceResolver, locates the foo.js script in either the webapp/resources or the webapp/other-resources folder:
<script type="text/javascript" src="<c:url value="/resources/foo.js" />">
5.2. The EncodedResourceResolver
This resolver attempts to find an encoded resource based on the Accept-Encoding request header value.
For example, we may need to optimize bandwidth by serving the compressed version of a static resource using gzip content coding.
To configure an EncodedResourceResolver, we need to configure it in the ResourceChain, just as we configured the PathResourceResolver:
registry
.addResourceHandler("/other-files/**")
.addResourceLocations("file:/Users/Me/")
.setCachePeriod(3600)
.resourceChain(true)
.addResolver(new EncodedResourceResolver());
By default, the EncodedResourceResolver is configured to support br and gzip codings.
So the following curl request will get the zipped version of the Home.html file located in the file system in the Users/Me/ directory:
curl -H "Accept-Encoding:gzip"
http://localhost:8080/handling-spring-static-resources/other-files/Hello.html
Notice how we’re setting the header’s “Accept-Encoding” value to gzip. This is important because this particular resolver will only kick in if the gzip content is valid for the response.
Finally, note that, same as before, the compressed version will remain available for the period of time it is cached in the browser, which in this case is 3600 seconds.
5.3. Chaining ResourceResolvers
To optimize resource lookup, ResourceResolvers can delegate the handling of resources to other resolvers. The only resolver that can’t delegate to the chain is the PathResourceResolver, which we should add at the end of the chain.
In fact, if the resourceChain isn’t set to true, then by default only a PathResourceResolver will be used to serve resources. Here we’re chaining the PathResourceResolver to resolve the resource if the GzipResourceResolver is unsuccessful:
@Override
public void addResourceHandlers(ResourceHandlerRegistry registry) {
registry
.addResourceHandler("/js/**")
.addResourceLocations("/js/")
.setCachePeriod(3600)
.resourceChain(true)
.addResolver(new GzipResourceResolver())
.addResolver(new PathResourceResolver());
}
Now that we’ve added the /js/** pattern to the ResourceHandler, let’s include the foo.js resource, located in the webapp/js/ directory in our home.html page:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<html>
<head>
<link href="<c:url value="/resources/bootstrap.css" />" rel="stylesheet" />
<script type="text/javascript" src="<c:url value="/js/foo.js" />"></script>
<title>Home</title>
</head>
<body>
<h1>This is Home!</h1>
<img alt="bunny hop image" src="<c:url value="files/myImage.png" />" />
<input type = "button" value="Click to Test Js File" onclick = "testing();" />
</body>
</html>
It’s worth mentioning that, as of Spring Framework 5.1, the GzipResourceResolver has been deprecated in favor of the EncodedResourceResolver. Therefore, we should avoid using it in the future.
6. Additional Security Configuration
If using Spring Security, it’s important to allow access to static resources. We’ll need to add the corresponding permissions for accessing the resource URL:
<intercept-url pattern="/files/**" access="permitAll" />
<intercept-url pattern="/other-files/**/" access="permitAll" />
<intercept-url pattern="/resources/**" access="permitAll" />
<intercept-url pattern="/js/**" access="permitAll" />
7. Conclusion
In this article, we illustrated various ways in which a Spring application can serve static resources.
The XML-based resource configuration is a legacy option that we can use if we can’t go down the Java configuration route yet.
Spring 3.1. came out with a basic programmatic alternative through its ResourceHandlerRegistry object.
Finally, the new out of the box ResourceResolvers and ResourceChainRegistration object that shipped with Spring 4.1. offers resource loading optimization features, like caching and resource handler chaining, to improve efficiency in serving static resources.
As always, the full example is available over on Github. Additionally, Spring Boot related source codes are also available in this project.