-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Zuul returns "400 Bad Request" randomly for chunked responses #261
Comments
What is the origin routing code you are using? This seems like it may be a spring boot issue. Is there a stack trace or anything when this happens? |
I was experiencing this problem today and it seems gone if you upgrade to the lastests version of spring boot and zuul |
@dgomezs what version of both seems to be fixing this issue? |
hey @sokie This is the config I have and that has been working for me.
I hope it helps |
I met this because I have wrote my own filter, In my filter I change the body size ,then the real content-length is not equals to the value in head. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Hey!
Sending a PUT request to an API through Zuul returns
400 Bad Request
randomly. If I send the same request directly to the API behind, it always works returning200 OK
, but if the request goes through Zuul, it sometimes returns200 OK
, sometimes fails.Analyzing packages with
tcpdump
shows an strange behaviour of one http request receiving two http responses, which it shouldn't happen at all.The API behind zuul is an Spring Boot application returning a
Single
object, and it sends chunks responses to Zuul. I've reproduced the same issue with this endpoint.inputStream
is reading a JSON file from the server to simulate the response. With this code, we get a400 Bad Request
one on every 10-15 requests.It also looks like if the
inputStream
reads a small file, no error is shown, but if the file goes above some bytes, it starts happening.Any help?
The text was updated successfully, but these errors were encountered: