-
Notifications
You must be signed in to change notification settings - Fork 54
Description
https://www.w3.org/TR/gpc/#gpc-support-resource includes (emphasis added)
A site MAY produce a resource at a .well-known URL in order for a site to represent the fact that it abides by GPC requests, at least where required to do so. The purpose of a GPC support resource is for a site to convey its awareness of and support for the Global Privacy Control. The support resource is not intended to convey whether the site abides by GPC requests from the user agent accessing the resource. By default, an origin's support is unknown.
A GPC support resource has the well-known identifier /.well-known/gpc.json relative to the origin server's URL [RFC8615].
An origin server that receives a valid GET request targeting its GPC support resource responds either with a successful response containing a machine-readable representation of the site-wide tracking status, as defined below, or a sequence of redirects that leads to such a representation (which MAY be provided by a server at another origin).
If https://subdomain.domain.example/.well-known/gpc.json contains ... gpc: true ..., does that claim that https://domain.example/ and https://othersub.domain.example/ also intend to abide by GPC requests, or does it only make that claim for https://subdomain.domain.example/? If it's meant to be local, you should replace all the "site"s here with "origin". If it's meant to be site-wide, probably the first "origin" should change to "site". If https://domain.example/ is meant to be able to make claims for https://subdomain.domain.example/ but not vice-versa, you'll need some more words.
(It would be a bit weird for https://subdomain.domain.example/ to be able to make claims for https://domain.example/, which is what the current wording says, but I don't know enough to say that it's wrong.)