Hi, it appears that any domain with Covid19 in the title is also being flagged. For example, our domain covid19cardiology.com is being blocked in some organizations. Interestingly, the netlify.app subdomain works just fine. Do you have any suggestions with regards to this issue? Thank you!
Hey @singamnv,
Unfortunately, I think weāre a little stuck for options here! You should be able to speak with your domain registrar who may be able to discuss if this is true? Unfortunately, because itās not something which weāre systematically a part of ā we canāt effectively help 
!
3 posts were split to a new topic: Hugo build failed with āerror calling Paginate: invoked multiple times with different argumentsā
Nice replyā¦itās been nice using your product
This thread was a good read. I tried doing some testing with cross-domain cookies (where they share the same apex domain) and ran into an issue where I couldnāt set a cookie with domain=netlify.app from a Netlify site I deployed to netlify.app domain. It worked fine though when I hooked up a custom domain. Now I understand why!
The reason I wanted to do this in the first place was because I like to write automated tests. I figured deploying sites to Netlify during CI, doing assertions using headless Chrome, and then deleting the Netlify sites when finished would be a good way to do it. I see now that Iād have to add more to the automated tests to set the custom domain and set the DNS records. Any advice for doing this without having to set DNS records, or is that the only way to go?
I think if you set the cookie for a specific subdomain that would work. You can use build environment variables:
This was actually cookies set by front end JS for the purpose of anonymously tracking users, not cookies set by the server.
That is expected behaviour as netlify.app is listed in the Public Suffix List. So you can set a cookie for subdomain.netlify.app but not netlify.app.
Yes, I know that now. I was saying that after spending hours troubleshooting why I couldnāt set a cookie for netlify.app so that my two Netlify sites could share it, I came across this thread and learned about the public suffix list:
āLots of reasons, but a big one among them is that weād like to leave the public suffix list , which we are on due to hosting millions of customer websites on *.netlify.com along with our own - we canāt currently share things like cookies between our *.netlify.com properties (www, app, community for instance).ā
Ah, thanks for that pointer! As an FYI weāll only be āleavingā the public suffix list on netlify.com domains, not your netlify.app domains, so the restriction will still be in effect for your sites unless you use custom domains.
hi there, unfortunately i donāt understand the question but i am going to try my best to answer - all sites are now .app sites. and yes, custom domains are supported.
1 Like
I am still clueless; What considerations should website owners on Netlify take into account when transitioning their site URLs from .com to .app?
You need take no action. This post is a notification about a change we made years ago.
Thank You, thatās great
1 Like