Brian Clozel 3c6b001349 Reuse existing async timeout in DefaultAsyncServerResponse ...

Prior to this commit, calling `DefaultAsyncServerResponse.writeAsync()`
would  unconditionally create a new `AsyncWebRequest` and install it
on the `WebAsyncManager`, even when one is already present for the
current request.
The functional web framework can do such a thing when returning a
`ServerResponse.async(future)` from a `HandlerFunction`; the
`HandlerFunctionAdapter` does install an async web request already.

This means that the async timeout configured at the application level
would be ignored and instead falling back to the Servlet container
default.

This commit makes the `DefaultAsyncServerResponse` skip async web
request creation it there is an existing one.

Fixes gh-37257

2026-09-08 11:48:40 +02:00

..

src

Reuse existing async timeout in DefaultAsyncServerResponse

2026-09-08 11:48:40 +02:00

spring-webmvc.gradle

Resolve URL path for versioned webjar directories

2026-05-01 21:47:06 +01:00