On Fri, Apr 26, 2024 at 7:20 PM Mark Thomas wrote:
>
> On 24/04/2024 17:52, Mark Thomas wrote:
>
>
>
> > My plan is to commit these changes to 11.0.x with the low risk parts
> > (e.g. new methods) back-ported. Then, once we can see what is left, we
> > can decide how quickly/slowly we want to
Mark,
On 4/26/24 13:17, Mark Thomas wrote:
On 24/04/2024 17:52, Mark Thomas wrote:
My plan is to commit these changes to 11.0.x with the low risk parts
(e.g. new methods) back-ported. Then, once we can see what is left, we
can decide how quickly/slowly we want to back-port the complete fix
On 24/04/2024 17:52, Mark Thomas wrote:
My plan is to commit these changes to 11.0.x with the low risk parts
(e.g. new methods) back-ported. Then, once we can see what is left, we
can decide how quickly/slowly we want to back-port the complete fix to
10.1.x and 9.0.x (the issue was reported
Hi all,
The Spring folks have pinged me on an issue reported to them. The short
version is that Tomcat doesn't support non-blocking reads of chunked
request bodies.
While we have nearly all of the pieces we need to fix this, the commit
is still going to be quite large involving quite a lot
Hi,
As you might have worked out from my commits, I'm working on a fix for
bug 60276 [1] to add gzip compression support to HTTP/2. As usual, I
want to reduce duplication / copy/paste so I am looking to re-use the
GzipOutputFilter from HTTP/1.1.
As I have been working on this it has become
