Spec "Referer" and "Origin" headers in reporting beacons.

[blu25]

This PR specs the following behavior:

• Setting the "Origin" header to the origin of the frame that invoked reportEvent() for destination URL events.
• Setting the "Origin" header to the worklet's origin (which we are calling reporting url declarer origin) for destination enum and automatic beacon events.
• Setting the "Referer" header to the ad frame root's origin (which we are calling initiator ancestor root origin) for automatic beacons triggered by component ad frames.
• Setting the "Referer" header to the origin of the frame that triggered the beacon for all beacons triggered not by component ads.

See this document for notes/reasonings on why things were done the way they were.

There will need to be a separate effort in the Protected Audience spec to set some of the values that these changes are expecting to be set. More specifically:

• The new reporting url declarer origin variable will need to be set during the asynchronously finish reporting when it invokes finalize a reporting destination.

---

Preview | Diff

[domfarolino]

Is this a draft or is this ready for my review?

[blu25]

Is this a draft or is this ready for my review?

It's back to draft after changes were made during the impl's code review. I'll re-request when it's ready for you to take a look.

[domfarolino]

Any idea why the latest preview does not seem to be updated? In the preview "declarer origin" can be null but I don't think that matches the spec text, right?

[blu25]

Any idea why the latest preview does not seem to be updated? In the preview "declarer origin" can be null but I don't think that matches the spec text, right?

I'm not sure. It seems to be working again since I uploaded the latest patch, so you should be good to look at the preview/diff.

[blu25]

Let's hold off on merging this until the latest discussion in the design doc is addressed.