From 41ab5e04290a3d3b824b5a884575fa9c954458be Mon Sep 17 00:00:00 2001 From: tbodt Date: Wed, 8 Jan 2025 04:11:08 -0800 Subject: [PATCH] hash -> encrypt (#10647) Co-authored-by: Sarah Rainsberger <5098874+sarah11918@users.noreply.github.com> --- src/content/docs/en/guides/server-islands.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/en/guides/server-islands.mdx b/src/content/docs/en/guides/server-islands.mdx index bee687c6a6991..e5e944bdccc0e 100644 --- a/src/content/docs/en/guides/server-islands.mdx +++ b/src/content/docs/en/guides/server-islands.mdx @@ -97,7 +97,7 @@ const productId = url.searchParams.get('product'); ## Reusing the encryption key -Astro uses [cryptography](https://developer.mozilla.org/en-US/docs/Glossary/Cryptography) to hash props passed to server islands to prevent accidentally leaking secrets. The props are hashed using a key that is generated during the build. +Astro uses [cryptography](https://developer.mozilla.org/en-US/docs/Glossary/Cryptography) to encrypt props passed to server islands to prevent accidentally leaking secrets. The props are encrypted using a key that is generated during the build. For most hosts, this happens transparently and there is nothing that you as a developer need to do. If you are using rolling deployments in an environment such as Kubernetes, you may run into issues where the frontend and backend are temporarily out of sync and the keys don't match.