You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to switch from an API Gateway fronted Lambda function running Apollo to an ALB, we encountered 400 errors when users made GET requests to the server.
Is this user error because we have not URL decoded the query string parameter before sending the request down, or is Apollo server expected to handle this for us? It doesn't seem like this was required when running with the API Gateway handler.
Link to Reproduction
I can't do this, as it requires provisioning AWS resources.
Reproduction Steps
Create an ALB and send a GET request with a query string parameter that is URL encoded JSON content.
The text was updated successfully, but these errors were encountered:
Issue Description
While trying to switch from an API Gateway fronted Lambda function running Apollo to an ALB, we encountered 400 errors when users made GET requests to the server.
The exception is thrown here:
https://github.com/apollographql/apollo-server/blob/main/packages/server/src/runHttpQuery.ts#L62
and I think it basically boils down to the fact that this:
https://github.com/apollographql/apollo-server/blob/main/packages/server/src/runHttpQuery.ts#L44
is not:
Is this user error because we have not URL decoded the query string parameter before sending the request down, or is Apollo server expected to handle this for us? It doesn't seem like this was required when running with the API Gateway handler.
Link to Reproduction
I can't do this, as it requires provisioning AWS resources.
Reproduction Steps
Create an ALB and send a GET request with a query string parameter that is URL encoded JSON content.
The text was updated successfully, but these errors were encountered: