RESOLVED FIXED 220902
PCM: Use different well-known locations for triggering and reporting attribution 
https://bugs.webkit.org/show_bug.cgi?id=220902
Summary PCM: Use different well-known locations for triggering and reporting attribution
John Wilander
Reported 2021-01-24 14:08:59 PST
The discussion in W3C Privacy CG decided that we should use distinct well-known URL paths for websites triggering attribution and for the browser reporting attribution (https://github.com/privacycg/private-click-measurement/issues/59): /.well-known/private-click-measurement/trigger-attribution /.well-known/private-click-measurement/report-attribution
Attachments
Patch (23.81 KB, patch)
2021-01-24 14:43 PST, John Wilander 		no flags
DetailsFormatted DiffDiff
Patch (25.41 KB, patch)
2021-01-24 16:37 PST, John Wilander 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2021-01-24 14:09:30 PST
<rdar://problem/73550632>
John Wilander
Comment 2 2021-01-24 14:43:27 PST
Created attachment 418242 [details] Patch
John Wilander
Comment 3 2021-01-24 16:37:57 PST
Created attachment 418244 [details] Patch
John Wilander
Comment 4 2021-01-24 16:38:29 PST
Fixed the iOS API test.
Brent Fulgham
Comment 5 2021-01-25 09:58:38 PST
Comment on attachment 418244 [details] Patch r=me
EWS
Comment 6 2021-01-25 10:28:47 PST
Committed r271799: <https://trac.webkit.org/changeset/271799> All reviewed patches have been landed. Closing bug and clearing flags on attachment 418244 [details].
Note You need to log in before you can comment on or make changes to this bug.