Rob Winch 242b831f20 Cache Control only written if not set ...

Previously Spring Security always wrote cache control headers and relied
on the application to override the values. This can cause problems with
cache control. For example, applications may only set cache control if
the header is not already set. Additionally, setting of Cache-Control
should disable writing of Pragma.

This commit delays writing headers until just before the response is
committed and only writes the Cache Control headers if they do not exist.

Fixes gh-2953

2016-03-15 12:30:37 -05:00

..

src

Cache Control only written if not set

2016-03-15 12:30:37 -05:00

pom.xml

Update pom.xml to 4.1.0.BUILD-SNAPSHOT

2016-03-14 00:51:35 -05:00

web.gradle

SEC-2915: groovy/gradle spaces->tabs

2015-03-25 13:08:59 -05:00