-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reset trailers on recycled response #4711
Labels
Specification
For all industry Specifications (IETF / Servlet / etc)
TCK
For various Specification Test Compatibility Kits (eg: Servlet, WebSocket, HTTP/2, etc)
Comments
gregw
added
Specification
For all industry Specifications (IETF / Servlet / etc)
TCK
For various Specification Test Compatibility Kits (eg: Servlet, WebSocket, HTTP/2, etc)
labels
Mar 25, 2020
|
I've also noted that sending and error has not reset either the transfer-encoding nor the trailers themselves! |
gregw
added a commit
that referenced
this issue
Mar 25, 2020
Whilst investigating #4711 for jetty-10, it was noticed that trailers are not nulled on recycled Response instances, nor on reset. Signed-off-by: Greg Wilkins <gregw@webtide.com>
sbordet
added a commit
that referenced
this issue
Mar 25, 2020
Test code cleanup. Added test for Response.reset(). Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
@gregw trailers done, but |
joakime
changed the title
Jetty-10 TCK Trailer tests failing
Reset trailers on recycled response
Apr 8, 2020
gregw
added a commit
that referenced
this issue
Nov 11, 2020
Reordered recycle in request and response to field order so that we can check that all fields are recycled.
gregw
added a commit
that referenced
this issue
Nov 16, 2020
passing asssociated TCK test so closing this one |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Specification
For all industry Specifications (IETF / Servlet / etc)
TCK
For various Specification Test Compatibility Kits (eg: Servlet, WebSocket, HTTP/2, etc)
The text was updated successfully, but these errors were encountered: