What's currently supported in PendingBeacon inherits from navigator.sendBeacon(), as one of the primary goal is to make a more reliable version of the latter.

Digging into discussion around sendBeacon()

I found a similar request to ask for customizing HTTP headers in Allow setting HTTP(S) headers in beacon w3c/beacon#30. The last comment was "(user should) be able to set custom headers/methods/etc, via fetch."
It points to a longer thread Add method to sendBeacon w3c/beacon#27 (comment). Looks like the developers were trying to extend from pre-existing sendBeacon() API shape and couldnot easily support other HTTP methods or customizing headers.
Not sure if any concerns about allowing customizing headers

Aside from the above, to allow customizing headers, the shape of API also needs a big update:

Currently only supports Get/Post via PendingGetBeacon & PendingPostBeacon, how do they interact with setHeader() which may lead to different method?
How to ensure "Follow third-party cookie rules for beacons"
(and probably more)

cc @philipwalton @clelland WDYT?

Supporting Headers in Pending Beacon #50

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions