Disable default spring security headers, allow spring cloud gateway to manage them #173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch disables the Spring Boot default security headers in
org.georchestra.gateway.security.GatewaySecurityConfiguration
.The default Spring Boot security headers, and the Spring Cloud Gateway
security headers handling are two different things, and the former was
preventing the later from taking over the configuration.
The sample configuration in
datadir/application.yaml
disables x-frame-options and x-content-type options response headers.It is a two step process, by one side, we need to remove the headers from downstream service responses,
by adding a RemoveResponseHeader default filter for each response header to remove.
On the other hand, the gateway's corresponding secure headers have to be disabled
(see spring.cloud.gateway.filter.secure-headers.disable.*)
For example: