From e2e9d28b289a7ad2f6bece7892f621b00b18cf62 Mon Sep 17 00:00:00 2001 From: Michael Macaulay <56690114+MichaelMacaulay@users.noreply.github.com> Date: Mon, 16 Dec 2024 16:41:00 -0500 Subject: [PATCH] Fix URLs --- nginx.conf | 1 - .../how-to-secure-api-keys-using-nextjs-server-components.mdx | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/nginx.conf b/nginx.conf index ab684474fe85..8e170e494aeb 100644 --- a/nginx.conf +++ b/nginx.conf @@ -86,7 +86,6 @@ http { rewrite ^/docs/([a-zA-Z][a-zA-Z])/supported-networks/near/$ $scheme://$http_host/docs/$1/cookbook/near/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/defining-a-subgraph/$ $scheme://$http_host/docs/$1/developing/creating-a-subgraph/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/arbitrum-faq/$ $scheme://$http_host/docs/$1/arbitrum/arbitrum-faq/ permanent; - rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/migrating-a-subgraph/$ $scheme://$http_host/docs/$1/cookbook/upgrading-a-subgraph/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/cookbook/quick-start/$ $scheme://$http_host/docs/$1/quick-start/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developer/assemblyscript-api/$ $scheme://$http_host/docs/$1/developing/graph-ts/api/ permanent; rewrite ^/docs/([a-zA-Z][a-zA-Z])/developing/assemblyscript-api/$ $scheme://$http_host/docs/$1/developing/graph-ts/api/ permanent; diff --git a/website/pages/en/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/en/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx index e37d83acbe78..5ae8b1b0a8dc 100644 --- a/website/pages/en/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx +++ b/website/pages/en/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx @@ -120,4 +120,4 @@ Start our Next.js application using `npm run dev`. Verify that the server compon ### Conclusion -By utilizing Next.js Server Components, we've effectively hidden the API key from the client-side, enhancing the security of our application. This method ensures that sensitive operations are handled server-side, away from potential client-side vulnerabilities. Finally, be sure to explore [other API key security measures](/cookbook/upgrading-a-subgraph/#securing-your-api-key) to increase your API key security even further. +By utilizing Next.js Server Components, we've effectively hidden the API key from the client-side, enhancing the security of our application. This method ensures that sensitive operations are handled server-side, away from potential client-side vulnerabilities. Finally, be sure to explore [other API key security measures](/querying/managing-api-keys/) to increase your API key security even further.