From a59406361a062cb477ce2ffedd5dc10583d88d5f Mon Sep 17 00:00:00 2001 From: dng Date: Mon, 12 Dec 2022 18:48:07 -0800 Subject: [PATCH] Update custom-domains.mdx --- apps/docs/pages/guides/platform/custom-domains.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/apps/docs/pages/guides/platform/custom-domains.mdx b/apps/docs/pages/guides/platform/custom-domains.mdx index 738f470847c..2690eb5f23b 100644 --- a/apps/docs/pages/guides/platform/custom-domains.mdx +++ b/apps/docs/pages/guides/platform/custom-domains.mdx @@ -85,11 +85,7 @@ supabase domains delete --project-ref foobarbaz --experimental As with the final activation stage of the process for setting up a custom domain, you'll need to update any references in your client code and OAuth providers from the custom domain to the Supabase-provisioned endpoints. -## Limitations - -Edge functions do not honor the custom domain setting and they still have to be invoked via the `foobarbaz.supabase.co` domain. - -# Vanity Subdomains +## Vanity Subdomains @@ -145,7 +141,7 @@ As with the final activation stage of the process for setting up a vanity subdom ## Limitations -Edge functions do not honor the vanity subdomain setting and they still have to be invoked via the `foobarbaz.supabase.co` domain. +Edge functions do not honor the custom domain or the vanity subdomain setting and they still have to be invoked via the `foobarbaz.supabase.co` domain. export const Page = ({ children }) =>