  ](https://img.shields.io/travis/marmelab/json-graphql-server.svg)  ](https://img.shields.io/travis/marmelab/json-graphql-server.svg)   mooncats (http json) graphql api / client
cryptopunks-graphql - (lite) cryptopunks (http json) graphql api / client
kittyverse-graphql - (lite) web client (helpers) for using CryptoKitties (HTTP JSON) GraphQL APIs
Extra types for graphql-ruby: JSON, Date, and BigInt
Imagine GraphQL alike query language for JSON based APIs usecase but with really pragmatic implementation using GET requests and query string includes
Imagine GraphQL alike query language for JSON based APIs usecase but with really pragmatic implementation using GET requests
A Ruby gem that provides a client for EYWA server with JSON-RPC communication, GraphQL support, and task management.
GraphQL interface over WCC::Contentful store
The middleware makes sure any request to specified paths would have been preflighted if it was sent by a browser. We don't want random websites to be able to execute actual GraphQL operations from a user's browser unless our CORS policy supports it. It's not good enough just to ensure that the browser can't read the response from the operation; we also want to prevent CSRF, where the attacker can cause side effects with an operation or can measure the timing of a read operation. Our goal is to ensure that we don't run the context function or execute the GraphQL operation until the browser has evaluated the CORS policy, which means we want all operations to be pre-flighted. We can do that by only processing operations that have at least one header set that appears to be manually set by the JS code rather than by the browser automatically. POST requests generally have a content-type `application/json`, which is sufficient to trigger preflighting. So we take extra care with requests that specify no content-type or that specify one of the three non-preflighted content types. For those operations, we require one of a set of specific headers to be set. By ensuring that every operation either has a custom content-type or sets one of these headers, we know we won't execute operations at the request of origins who our CORS policy will block.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.