-
Notifications
You must be signed in to change notification settings - Fork 37.7k
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
AsyncServerResponse interoperability issue with path variables #26239
Comments
@poutsma I just tested 5.3.2 snapshot to see the new block functionality in my tests, but something else is broken |
This commit makes sure that the matching pattern attributes is cleared when an async result has been obtained, so that the subsequent dispatch starts from scratch. Closes spring-projectsgh-26239
This should be fixed now. When it has finished building, could you please try a recent snapshot and see if that solves it for you as well? |
Tested against latest snapshot, and my test works correctly, so from my prospective also seems fixed. Thank you for the quick response! |
Tested again after this commit (snapshot build 84), everything still works fine. |
Thank you for the quick test run! I've refactored the code a bit in 2b77c08. It should do the same, but for extra reassurance: could you try a recent snapshot again, and report back? Thank you for being so quick about this. |
haha.. I refreshed the snapshot folder in maven waiting for the build to finish.. so I was ahead of you on that one |
Thanks! |
Affects: \5.3.2
There is an interoperability issue with the new
AsyncServerResponse
and routing functions. I tried to create a test in the webmvc project, but I'm afraid I don't know the framework well enough to reproduce it there.Instead there is a reproduction using springboot, with all the latest greatest spring, and webmvc is managed to 5.3.2-snapshot.
spring-webmvc-interop-bug
when routing a request that has path variables, we get routed correctly, and get to a function that returns a
ServerResponse.async
response, but during the handling of the response, the routing function is called again, and we get an exceptionorg.springframework.web.util.pattern.PatternParseException: Not allowed to capture 'pathVariable' twice in the same pattern
This does not happen if the response is a non async ServerResponse.
The text was updated successfully, but these errors were encountered: