-
Notifications
You must be signed in to change notification settings - Fork 908
Closed
Description
Hi there!
Hope someone could answer my questions about the RWS usage.
1. Is the .well-known folder required to be hosted on the "primary" domain (e.g. mydomain.com)? If so, do subdomains (e.g. service.mydomain.com & payment.mydomain.com) also need to host this folder?
2. Suppose we need to update the RWS config and opened up a PR which passed the CI automated-tests. How long does it take to get approvals?
PS: I've seen quite a few PRs being merged in more than 5 days after its opening. Hope there's somewhat method to accelerate the review process under urgent situation.
3. If the PR gets merged, does Chrome reflect the changes immediately or it'll take some time to?
4. Upon my local testing, I've found that the following settings result in the same behavior.
{"primary": "https://test.com", "associatedSites": ["https://mydomain.com/"]}
{"primary": "https://test.com", "serviceSites": ["https://mydomain.com/"]}
{"primary": "https://mydomain.com/", "associatedSites": ["https://test.com"]}
test.com
is the client site. mydomain.com
provides a 3rd party cookie.
test.com
needs to send request to mydomain.com
with that 3rd party cookie. In this case, I suppose we'll have to utilize the API document.requestStorageAccessFor
to grant access after user properly interacted with the page.
The doc says if I put "mydomain.com" into "serviceSites", when I request 3rd party storage access I'll get blocked. However, it's on the contrary. Wonder why this happened.
Metadata
Metadata
Assignees
Labels
No labels