• Andy Wilkinson's avatar
    Don't flush in ErrorPageFilter for < 400 response that's committed · 41cb5678
    Andy Wilkinson authored
    Previously, for a non-async response with a successful status (< 400),
    ErrorPageFilter would always call flushBuffer. This triggers an
    exception in Tomcat if the client has closed the connection before the
    response has been fully sent. In this case, Tomcat treats the response
    as successful and commits it before control returns to the filter.
    
    This commit updates ErrorPageFilter to only perform the flush if the
    response has not already been committed, leaving any further flushing
    that may be necessary to be handled by the servlet container.
    
    Fixes gh-1938
    41cb5678
Name
Last commit
Last update
docs Loading commit data...
eclipse Loading commit data...
spring-boot Loading commit data...
spring-boot-actuator Loading commit data...
spring-boot-autoconfigure Loading commit data...
spring-boot-cli Loading commit data...
spring-boot-dependencies Loading commit data...
spring-boot-docs Loading commit data...
spring-boot-full-build Loading commit data...
spring-boot-integration-tests Loading commit data...
spring-boot-parent Loading commit data...
spring-boot-samples Loading commit data...
spring-boot-starters Loading commit data...
spring-boot-tools Loading commit data...
spring-boot-versions Loading commit data...
.gitignore Loading commit data...
.settings-template.xml Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING.adoc Loading commit data...
README.adoc Loading commit data...
pom.xml Loading commit data...