From a4e569f06786cf0aace9164886fcaee4d364700a Mon Sep 17 00:00:00 2001 From: Jonathan Summers-Muir Date: Tue, 24 Oct 2023 13:40:50 +0800 Subject: [PATCH] Update network-restrictions.mdx (#18422) --- apps/docs/pages/guides/platform/network-restrictions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/docs/pages/guides/platform/network-restrictions.mdx b/apps/docs/pages/guides/platform/network-restrictions.mdx index cb86b8008fd..62c243e79e1 100644 --- a/apps/docs/pages/guides/platform/network-restrictions.mdx +++ b/apps/docs/pages/guides/platform/network-restrictions.mdx @@ -66,7 +66,7 @@ Restrictions applied successfully: true ## Limitations -- The current iteration of Network Restrictions applies to connections to Postgres and PgBouncer and doesn't currently apply to APIs offered over HTTPS (e.g., PostgREST, Storage, and Auth). +- The current iteration of Network Restrictions applies to connections to Postgres and PgBouncer and doesn't currently apply to APIs offered over HTTPS (e.g., PostgREST, Storage, and Auth). This includes using Supabase client libraries like [supabase-js](https://supabase.com/docs/reference/javascript). - Network Restrictions should not be used if you need to connect to your Postgres database using Edge Functions. - [Supavisor](https://github.com/supabase/supavisor/) does not currently support Network Restrictions.