You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello ! First, thanks a lot for your awesome library !
I didn't see that this issue has already been reported even if some are close to what I encountered.
I get a conflict with ErrorPageFilter in non-embedded containers, the result is that the Spring Boot Whitelabel Error Page doesn't display. I have an error log similar to this one : 2018-03-06 22:05:05.752 ERROR 8600 --- [nio-8080-exec-6] o.s.boot.web.support.ErrorPageFilter : Cannot forward to error page for request [/test] as the response has already been committed. As a result, the response may have the wrong status code. If your application is running on WebSphere Application Server you may be able to resolve this problem by setting com.ibm.ws.webcontainer.invokeFlushAfterService to false
The issue can easily be reproduced with a plain Spring Boot application like this one. Deploy it to Tomcat (non-embedded) and hit a path that is unknown to the server.
The text was updated successfully, but these errors were encountered:
Yes, actually the company I'm working for use it to handle all exceptions that may not have been handled in specific handler classes and/or handler methods.
Hello ! First, thanks a lot for your awesome library !
I didn't see that this issue has already been reported even if some are close to what I encountered.
I get a conflict with ErrorPageFilter in non-embedded containers, the result is that the Spring Boot Whitelabel Error Page doesn't display. I have an error log similar to this one :
2018-03-06 22:05:05.752 ERROR 8600 --- [nio-8080-exec-6] o.s.boot.web.support.ErrorPageFilter : Cannot forward to error page for request [/test] as the response has already been committed. As a result, the response may have the wrong status code. If your application is running on WebSphere Application Server you may be able to resolve this problem by setting com.ibm.ws.webcontainer.invokeFlushAfterService to false
The issue can easily be reproduced with a plain Spring Boot application like this one. Deploy it to Tomcat (non-embedded) and hit a path that is unknown to the server.
The text was updated successfully, but these errors were encountered: