-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CORS headers to list resource #1433
Comments
are you suggesting this added to the headers or the file itself? |
Added to the HTTP headers of the resource. |
The weird thing is, the rest of the site seems to have this header, eg https://publicsuffix.org/list/, but the list itself does not. |
Is this fixed? The list appears to have CORS headers now. |
I believe that Mozilla Ops are transitioning CDN hosting of the list. This
may explain some of the diversity of messaging headers seen between Dec 15
and now.
|
But, is this is issue intentionally fixed, or accidentally fixed and may be unfixed? |
@jakearchibald While I agree with you in principle, is there a particular reason why it would be useful for a website to pull in the PSL? And to answer the original question, those were added intentionally and for the entire site. |
Allow websites to access https://publicsuffix.org/list/public_suffix_list.dat by giving the resource the following header:
The text was updated successfully, but these errors were encountered: