-
Notifications
You must be signed in to change notification settings - Fork 368
Fix for the InputStream caching cases for Servlets #5904
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
Conversation
Signed-off-by: Maxim Nesen <maxim.nesen@oracle.com>
61e31e9 to
497adbb
Compare
|
Is it possible to migrate the part of fix to 3.1.* versions branch? Specifically the following changes, caching wrappedStream to avoid multiple calls to request.getInputStream from InputStreamWrapper: ? Let me clarify: We get the following errors starting from 3.1.8 jersey version: The cause is that org.glassfish.jersey.servlet.WebComponent$5.getWrapped(WebComponent.java:431) calls actually getInputStream for every single byte, thus doesn't iterate over a single stream, rather retrieves a stream every time from request. If we want to make a stream wrapper that allow multiple reads of the source stream, then we need to return a new stream every time getInputStream() is called, otherwise we don't have any hint on whether this is just an iteration or a start of a new iteration of a stream. Thanks in advance. |
|
@asharayev Sure, it already is in 3.1 |
Indeed! Thanks for the info! |
No description provided.