From a268cdb9135ea3572e27620edee7fa26140b3c2a Mon Sep 17 00:00:00 2001 From: Juergen Hoeller Date: Wed, 28 Oct 2015 16:06:59 +0100 Subject: [PATCH] Fixed javadoc links to setCacheSeconds --- .../web/servlet/support/WebContentGenerator.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-webmvc/src/main/java/org/springframework/web/servlet/support/WebContentGenerator.java b/spring-webmvc/src/main/java/org/springframework/web/servlet/support/WebContentGenerator.java index 86fa88c677..fda8819180 100644 --- a/spring-webmvc/src/main/java/org/springframework/web/servlet/support/WebContentGenerator.java +++ b/spring-webmvc/src/main/java/org/springframework/web/servlet/support/WebContentGenerator.java @@ -38,11 +38,11 @@ import org.springframework.web.context.support.WebApplicationObjectSupport; * {@link org.springframework.web.servlet.HandlerAdapter}. * *

Supports HTTP cache control options. The usage of corresponding HTTP - * headers can be controlled via the {@link #setCacheSeconds "cacheSeconds" + * headers can be controlled via the {@link #setCacheSeconds "cacheSeconds"} * and {@link #setCacheControl "cacheControl"} properties. * *

NOTE: As of Spring 4.2, this generator's default behavior changed when - * using only {@link #setCacheSeconds)}, sending HTTP response headers that are in line + * using only {@link #setCacheSeconds}, sending HTTP response headers that are in line * with current browsers and proxies implementations (i.e. no HTTP 1.0 headers anymore) * Reverting to the previous behavior can be easily done by using one of the newly * deprecated methods {@link #setUseExpiresHeader}, {@link #setUseCacheControlHeader}, -- GitLab