dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-06 01:45:10 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #14664 from supabase/dd/docs-cust-domains

Browse Source 
chore: remove edge function limitation for custom domains
This commit is contained in:
Lakshan Perera authored and GitHub committed 2023-05-30 06:56:04 +10:00
2 parents 2131a400de d0770fa5ae
commit 12266d760e
1 file changed
-1
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/pages/guides/platform/custom-domains.mdx
-1
View File
@@ -141,7 +141,6 @@ As with the final activation stage of the process for setting up a vanity subdom
## Limitations
- 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.
- A Supabase project can—at this time—use either a Custom Domain or a Vanity Subdomain, but not both.
- Some authentication flows like Sign-in with Twitter set cookies to track the progress of the flow. Make sure you use only one domain in your frontend application for this reason. Mixing calls to the Supabase domain `foobarbaz.supabase.co` and your custom domain could cause those flows to stop working due to the [Same Origin Policy](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy) enforced on cookies by the browser.