-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
400 (Bad Request) in relay-treasurehunt example #388
Comments
I can't repro this locally on master |
I just took the last master and the issue is still here. What's weird is that the graphQL server is supposed to run on http://localhost:8080 but the screenshot above shows that graphQL requests that fail are emitted on http://localhost:3000/graphQL. Below is the same request, reproduced via curl:
And here the same request but played on 8080 port (it works correctly):
Since I did not touch in any way to the code of the example, how does it come that graphQL requests are emitted on the wrong domain (localhost:3000 instead of localhost:8080)? Is it there anything I can do to pinpoint the issue more precisely? Thanks! |
Ok I found the issue. It was a local mitmproxy install (https://mitmproxy.org/) that was somehow messing with my request to graphql. Not sure why but after un-installing it, the example works correctly. Thanks. |
Glad to hear that you got to the bottom of this! |
Hi,
I can't get the relay-treasurehunt example to work. I get this errors when loading http://localhost:3000 into my chrome browser:
I am running node v4.1.0 on a Mac os x Yosemite 10.10.3, chrome Version 45.0.2454.99 (64-bit) and Relay master branch at commit d2c821e.
I ran
npm run update-schema
thennpm install
and finallynpm start
to run the example server. Did I miss something?Thanks.
The text was updated successfully, but these errors were encountered: