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
The test expects the header not to be set, but fails because we are allowing the headers to be set after sendError.
The text was updated successfully, but these errors were encountered:
janbartel
added
Bug
For general bugs on Jetty side
TCK
For various Specification Test Compatibility Kits (eg: Servlet, WebSocket, HTTP/2, etc)
labels
Apr 14, 2023
janbartel
changed the title
jetty-12 ee10 ServletApiResponse.sendError does not mark the response as being committed
jetty-12 ee10 ServletApiResponse.addIntHeader does not ignore headers after response committed
Apr 24, 2023
The javadoc for
HttpServletResponse.sendError
says:After using this method, the response should be considered to be committed and should not be written to.
The tck test:
does a
sendError
followed by setting some headers:The test expects the header not to be set, but fails because we are allowing the headers to be set after
sendError
.The text was updated successfully, but these errors were encountered: