spring-framework

Spring Framework

Tree: e1e8c165db

Brian Clozel e1e8c165db Avoid setting special Content-* response headers for Tomcat As of gh-21783, Spring WebFlux uses a `TomcatHeadersAdapter` implementation to directly address the native headers used by the server. In the case of Tomcat, "Content-Length" and "Content-Type" headers are processed separately and should not be added to the native headers map. This commit improves the `HandlerAdapter` implementation for Tomcat and removes those headers, if previously set in the map. The adapter already has a section that handles the Tomcat-specific calls for such headers. Fixes gh-24387	6 years ago
..
src	Avoid setting special Content-* response headers for Tomcat	6 years ago
spring-web.gradle	Upgrade to RxJava 2.2.17, OkHttp 3.14.6, Hibernate ORM 5.3.15	6 years ago

Brian Clozel e1e8c165db Avoid setting special Content-* response headers for Tomcat

As of gh-21783, Spring WebFlux uses a `TomcatHeadersAdapter`
implementation to directly address the native headers used by the
server.

In the case of Tomcat, "Content-Length" and "Content-Type" headers are
processed separately and should not be added to the native headers map.

This commit improves the `HandlerAdapter` implementation for Tomcat and
removes those headers, if previously set in the map. The adapter
already has a section that handles the Tomcat-specific calls for such
headers.

Fixes gh-24387

6 years ago

src

Avoid setting special Content-* response headers for Tomcat

6 years ago

spring-web.gradle

Upgrade to RxJava 2.2.17, OkHttp 3.14.6, Hibernate ORM 5.3.15

6 years ago