From ac3847bf4a52438fc90aa4dc61ff25a8fac31685 Mon Sep 17 00:00:00 2001 From: Brian Clozel Date: Wed, 17 Feb 2016 16:48:28 +0100 Subject: [PATCH] Clarify Javadoc for CacheControl.noCache,noStore This change makes clear that this is the intent of the CacheControl API not to provide a way to configure both "no-cache" and "no-store" directives for the "Cache-Control" header. Issue: SPR-13780 --- .../src/main/java/org/springframework/http/CacheControl.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-web/src/main/java/org/springframework/http/CacheControl.java b/spring-web/src/main/java/org/springframework/http/CacheControl.java index fbdc5691a1c..c99333445f3 100644 --- a/spring-web/src/main/java/org/springframework/http/CacheControl.java +++ b/spring-web/src/main/java/org/springframework/http/CacheControl.java @@ -114,7 +114,7 @@ public class CacheControl { * clients sending conditional requests (with "ETag", "If-Modified-Since" headers) and the server responding * with "304 - Not Modified" status. *

In order to disable caching and minimize requests/responses exchanges, the {@link #noStore()} directive - * should be used. + * should be used instead of {@link #noCache()}. * @return {@code this}, to facilitate method chaining * @see rfc7234 section 5.2.2.2 */