-
Notifications
You must be signed in to change notification settings - Fork 272
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
v1.59.0 Sends subgraph requests without Content-Length header #6503
Comments
@joemccall86 Thanks for raising the issue. Just to confirm, are you actually using Router v1.58.1 and upgrading to v1.59.0? There is no version 0.59.0 |
Yes, sorry about that. Fixed the title and description. |
AFAIK the I don't recall anything in the changes we made in 1.59.0 that would cause changes to the subgraph requests. When you say the subgraph "could not parse" the request, do you have any more specifics? Are we looking at garbled non-JSON bytes, missing/wrong headers, anything like that, something else? |
I did some troubleshooting by looking at the subgraph request content: v1.58.1
v1.59.0:
A couple things I noticed:
I suspect that our affected subgraph (which is a legacy monolith) is having a hard time processing requests without |
Describe the bug
When upgrading from router v0.58.1 to v0.59.0, one of our subgraphs in Ruby could not parse the request. I enabled request/response logging in router and discovered a difference in the request behavior:
v1.58.1:
v1.59.0:
Our subgraph doesn't support this "Streaming" mode. We do not have compression enabled for any of our subgraphs either. The only difference is the version of router.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The subgraph still receives the full body of the request
Output
If applicable, add output to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: