Skip to content

Commit 7d83174

Browse files
Openblocks-docsgitbook-bot
Openblocks-docs
authored andcommitted
GITBOOK-134: Update GraphQL
1 parent edb2af2 commit 7d83174

File tree

2 files changed

+7
-3
lines changed

2 files changed

+7
-3
lines changed

docs/data-sources/connect-to-databases-1/graphql.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,11 @@ The following is an example of connecting to [GitHub GraphQL API](https://docs.g
3131

3232
## SSL Cert Verification
3333

34-
For detailed information, see [SSL Cert Verification](graphql.md#ssl-cert-verification).
34+
For detailed information, see [SSL Cert Verification](rest-apis.md#ssl-cert-verification).
35+
36+
## Forward cookies
37+
38+
For detailed information, see [Forward cookies](rest-apis.md#forward-cookies).
3539

3640
## Create a GraphQL query
3741

docs/data-sources/connect-to-databases-1/rest-apis.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
# REST APIs
1+
# REST API
22

33
## Connect REST API to Openblocks
44

@@ -35,7 +35,7 @@ Note that for self-signed certificate, the information should be provided in .[P
3535

3636
<figure><img src="../../.gitbook/assets/rest-api-5.png" alt=""><figcaption></figcaption></figure>
3737

38-
## Forward Cookies
38+
## Forward cookies
3939

4040
If you are self-hosting Openblocks in your own domain, you can make REST API requests with cookies to existing services under that domain. You can either toggle the option "Forward all cookies" or specify certain cookies to forward in the text box. This feature can be helpful in cases where you use cookies to share common context (like identity info in JWT format) across different services.
4141

0 commit comments

Comments
 (0)