Skip to content
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

A empty JSON body is always set when proxying GET request #475

Open
williamchong opened this issue Dec 31, 2020 · 1 comment
Open

A empty JSON body is always set when proxying GET request #475

williamchong opened this issue Dec 31, 2020 · 1 comment

Comments

@williamchong
Copy link

Situation: I am proxying to a server with google load balancer, which does not accept GET request with any body.
I observed that even if I did not set any body in my original GET request, the proxied request always contain a empty JSON object body {} , which causes a HTTP 400 from my load balancer.

A sample failing test case, the request body always contains {}
williamchong@ba97f57

Expected: If the original GET request does not contain any body, no body should be set in the proxied request

@ianmaccallum
Copy link

I got around this by setting parseReqBody to false for get requests. Not ideal but it's working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants