Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Any plan to add an insecure option? #687

Closed
schickling opened this issue Sep 28, 2017 · 1 comment
Closed

Any plan to add an insecure option? #687

schickling opened this issue Sep 28, 2017 · 1 comment

Comments

@schickling
Copy link
Member

Issue by arthens
Thursday Sep 28, 2017 at 00:04 GMT
Originally opened as https://github.com/graphcool/cli/issues/285


Something similar to what apollo-codegen does.

Just ran into this problem because our local setup is https only but it uses self-signed certificates, which makes graphql get-chema dev fail with:

request to https://localhost/graphql failed, reason: unable to verify the first certificate

Running NODE_TLS_REJECT_UNAUTHORIZED=0 graphql get-schema dev fixes the problem, but it might be useful to have a documented option like graphql --insecure get-schema dev or graphql get-schema --insecure dev

@schickling
Copy link
Member Author

This issue was moved to Urigo/graphql-cli#17

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

No branches or pull requests

1 participant