Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cross origin policy headers #2740

Closed
HKalbasi opened this issue Jan 19, 2022 · 2 comments
Closed

Cross origin policy headers #2740

HKalbasi opened this issue Jan 19, 2022 · 2 comments
Labels
C-feature Category: feature. This is adding a new feature.

Comments

@HKalbasi
Copy link

Several features of browser is not enabled due specture, unless a page declare itself as cross origin isolated by sending coop and coep headers to the browser. Notably, sharedArrayBuffer feature need those headers, which is required for testing rust programs with thread in web assembly.

These headers are designed to be the new default, and I expect that increasingly more features and webpages will need them. But I don't know your policy about headers and if these headers fit it.
@HKalbasi HKalbasi added the C-feature Category: feature. This is adding a new feature. label Jan 19, 2022
@seanmonstar
Copy link
Member

What specifically are you asking for? If a server can send these? It certainly can, you can send any headers in a response.

@HKalbasi
Copy link
Author

Ah, wrong repository. I just meant hyperium/http#460. Sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-feature Category: feature. This is adding a new feature.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@seanmonstar @HKalbasi