12.0.x: Rework consumeAvailable() mechanism#14007
Conversation
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
gregw
left a comment
There was a problem hiding this comment.
I'm a bit more concerned about this now, as I didn't realise that HttpStreamOverHttp1#consumeAvailable made the connection non-persistent.
If this is the case, it is a little bit redundant as we have the method org.eclipse.jetty.server.ResponseUtils#ensureConsumeAvailableOrNotPersistent, which does a much better job of being non persistent.
I think we need to look a little closer before moving on, and maybe document a b it more
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Out of curiosity, I tried disabling the |
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
|
I pushed the removal of How does that look? |
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
|
@gregw I've reworked the whole |
consumeAll() behavior in ChannelStateconsumeAvailable() mechanism
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
gregw
left a comment
There was a problem hiding this comment.
Thinking on this one for a day...
jetty-core/jetty-server/src/main/java/org/eclipse/jetty/server/ResponseUtils.java
Show resolved
Hide resolved
gregw
left a comment
There was a problem hiding this comment.
This is good. The HttpGenerator does all the headers required.
consumeAvailable() mechanismconsumeAvailable() mechanism
Started with a fix for a comment detailing the
consumeAvailable()behavior that is partially incorrect, ended up reworking theconsumeAvailable()mechanism.See #13934 (comment)
See #14026 for the 12.1.x version of this PR.