Menu

What the Accept Header Decides on Our Own Site: Cloudflare's Beacon Tag Rides In or Out, and the API Host That Ignores It
📰

What the Accept Header Decides on Our Own Site: Cloudflare's Beacon Tag Rides In or Out, and the API Host That Ignores It

DEV Community: webdev·OnePassApps·6 days ago
#5QlxbQkH
#devtowebdev#devto#dev#header#html
Reading 0:00
15s threshold

I work on OnePassApps - this is our own site, and every number below was measured today, 11 November 2026, from outside the browser, signed out, over plain HTTPS, with no cookies and no JavaScript.

An earlier post of ours measured that the byte length of one of our pages moves with the Accept header the client sends, and left the mechanism open. This post opens it: which part of the request decides it, what is added and removed, and what the API host does with the same header.

What I measured

13 Accept header shapes on the app host home page, 3 fetches each: 39 requests

2 more app-host routes, 2 shapes each: 4 requests

7 API routes x 6 Accept values: 42 requests

85 requests carry the numbers in this post, every one of them to our two hosts, from one network.

On the app host, one header decides whether the beacon ships

Across all 13 shapes the home page came back in exactly two lengths, and every shape returned the same length on all three fetches: 25,011 bytes or 24,644 bytes.

Accept header sent…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.