GQL config question #54

New Issue

2024-08-20T13:33:44Z

zramsay commented

2024-08-20 13:33:44 +00:00

Where can we find the config section for the GraphQL endpoint in the laconid container?

We would have to make a few cors adjustments. We actually expected to find them in /root/.laconicd/config/app.toml or /root/.laconicd/config/config.toml. Some qpl flags at the laconicd binary have already been found.

Or have the settings of the GraphQL endpoint perhaps been derived from another endpoint?

Change Request: Add a GraphQL endpoint section into config.toml or app.toml

Where can we find the config section for the GraphQL endpoint in the laconid container? We would have to make a few cors adjustments. We actually expected to find them in /root/.laconicd/config/app.toml or /root/.laconicd/config/config.toml. Some qpl flags at the laconicd binary have already been found. Or have the settings of the GraphQL endpoint perhaps been derived from another endpoint? Change Request: Add a GraphQL endpoint section into config.toml or app.toml

ashwin commented

2024-08-20 13:49:33 +00:00

We would have to make a few cors adjustments.

Which ones in particular?

> We would have to make a few cors adjustments. Which ones in particular?

dboreham commented

2024-08-20 13:51:10 +00:00

I this works in my mainnet-laconic setup. I'll see where it gets configured.

dboreham commented

2024-08-20 17:43:23 +00:00

Did some checking, and it appears in my deployments cors wildcard is enabled by default. I don't think we explicitly enable it:

$ curl -H "Origin: http://example.com" --verbose http://testnet-a-2.dev.vaasl.io:9473/api
*   Trying 204.130.133.218:9473...
* Connected to testnet-a-2.dev.vaasl.io (204.130.133.218) port 9473 (#0)
> GET /api HTTP/1.1
> Host: testnet-a-2.dev.vaasl.io:9473
> User-Agent: curl/7.81.0
> Accept: */*
> Origin: http://example.com
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 422 Unprocessable Entity
< Access-Control-Allow-Origin: *
< Content-Type: application/json
< Vary: Origin
< Date: Tue, 20 Aug 2024 17:42:23 GMT
< Content-Length: 110

Did some checking, and it appears in my deployments cors wildcard is enabled by default. I don't think we explicitly enable it: ``` $ curl -H "Origin: http://example.com" --verbose http://testnet-a-2.dev.vaasl.io:9473/api * Trying 204.130.133.218:9473... * Connected to testnet-a-2.dev.vaasl.io (204.130.133.218) port 9473 (#0) > GET /api HTTP/1.1 > Host: testnet-a-2.dev.vaasl.io:9473 > User-Agent: curl/7.81.0 > Accept: */* > Origin: http://example.com > * Mark bundle as not supporting multiuse < HTTP/1.1 422 Unprocessable Entity < Access-Control-Allow-Origin: * < Content-Type: application/json < Vary: Origin < Date: Tue, 20 Aug 2024 17:42:23 GMT < Content-Length: 110 ```

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/laconicd#54