Re: [whatwg/url] Feature proposal: eTLD+1 web API (#528)

This is something we could use at Surfly. Here's our use case:

At Surfly, we are building an [application-level proxy](https://www.surfly.com/blog/exploring-middleware-superpowers-with-surfly-proxy-technology/). Part of the sandbox system is URL encoding.
We have an encoding scheme that maps arbitrary URLs to URLs within our own domain. At the same time, we want to make use of same-origin policy, and **replicate the cookie behaviour**. Since cookie scopes depend heavily on the site, we need to know whether a specific cookie will be processed by the browser, or ignored.

For example, if an app does `document.cookie = 'ignore=this; domain=co.uk'`, the cookie will not be set. While translating this into the sandbox domain, we need to detect this.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/528#issuecomment-942638760