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.

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

CORs Requests #279

Open
dgstpierre opened this issue Dec 17, 2021 · 4 comments
Open

CORs Requests #279

dgstpierre opened this issue Dec 17, 2021 · 4 comments

Comments

@dgstpierre
Copy link

When using XMLHttpRequest I don't need to worry about setting any accept-ch headers. I also avoid the costly overhead of a preflight call by limiting the headers sent. How will we be able to make third party API calls ensuring that the detailed ua client hints are sent and not introducing a preflight?

@Sora2455
Copy link

By adding the results of the UA JA API as part of the JSON body?

@dgstpierre
Copy link
Author

We can do this as with any data. Just seems that we are adding lots of overhead for something that was seamless before.

@nicjansma
Copy link

nicjansma commented May 31, 2022

Accept-CH can only be applied to the base page's HTTP response -- setting it on outgoing Fetch/XHRs will have no effect.

(then you would add a Permissions-Policy on the same base page HTTP response to delegate the required hints to the XHR domain)

@frankykubo
Copy link

Hello,

so if I understand this right @nicjansma , there is and probably will not be an approach to include high-entropy UA client hints like Arch without manually appending them to XHR's via JS Client hints API?

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants