New fetch mode "foriegn-cors"

💡 Ideas
,
1

In many use cases of fetching data from cross origins, It doesn't matter "who" fetchs the data and data will be the same for every one. In those cases, cors is just a trouble and people often use cors proxies as a workaround.

Foriegn-cors

This mode fetch content as a standalone native app and don't send any browser data, such as cookies, preferred language, ... .

Why?

  • It fix most cases of cors problems
  • No need for cors-proxy
    • no third party down time or gone away (like dead cors.io or crossorigin.me)
    • no risk of man in the middle by proxy
  • Fill the gap between native app and web app
1 Like
2

Both fetch and CORS are not part of JS, they're part of HTML (the browser). I'd suggest pursuing this there.

1 Like
3

OK. Can you please give me a link to HTML forum, Or if it does not exist, Where and How I can start?

4

I think it's https://discourse.wicg.io but I'm not sure.

1 Like
5

I clone it to wicg discource. link: https://discourse.wicg.io/t/proposal-new-fetch-mode-foreign-cors/4753