Beacon requests will fail when attempting to send more than 64k of data

[rr0214]

When sending beacon (unload) requests using the agent, there is no limit in place for the amount of data added to the body of that request.

According to this post, most browsers (at least at the time) implemented a 64k limit on the maximum size of data allowed to be sent in a given beacon (Edge & Firefox) or navigation context (Chrome): https://github.com/w3c/beacon/issues/38This issue came up in a GTSE ticket with a similar behavior in Safari for iOS. An unload session trace harvest exceeded 64k in length and failed.

Answer question: Is this still an issue (github issue from 2016) How often this happens? How close to this limit? Size of messages consumer sees from the agent.

check how large our request is and how much space is available.

Effort: Medium, open questions

[rr0214]

The first step needs to be instrumentation to measure impact.

[workato-integration]

https://issues.newrelic.com/browse/NEWRELIC-4743

[workato-integration]

Jira CommentId: 105498
Commented by jporter:

Validated: Beacons do limit to 64k, and this is checked across all active beacons at once (meaning aggregate > 64k causes cancel as well)

[workato-integration]

This issue won't be actioned.