-
Notifications
You must be signed in to change notification settings - Fork 657
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
Reactor Netty Hangs on Response 304 #465
Comments
Hi, According to the specification there is:
I was able to reproduce the scenario, here is what happens: The request to the
Then the
@smaldini @rstoyanchev @spencergibb Should we silently remove @fifothekid Regards, |
I've just opened a related issue |
Fixed with #467 |
…full empty message Related to #465
I have a Spring Cloud Gateway based API Gateway which points to a back-end service implemented in an older version of Spring Boot (blocking). When I send a PUT request that would return a status 204 response, it works both when sending the request directly to the back-end and to the API Gateway as expected. However, when I send a PUT request that would return a 304, it would work normally on the back-end but on the API Gateway it would give me a partial result and time-out after hanging.
Here is the result for the 204 responses:
And the ones for 304:
The trace log for both Spring Cloud Gateway and Reactor-Netty looks like this
A trace log for the whole application is too big to be attached to this message, but the most important part is this at the end:
I'm on Windows 10, using Finchley.SR1 and spring-boot-starter-parent 2.0.5.RELEASE.
Any help would be appreciated
The text was updated successfully, but these errors were encountered: