Skip to content
  • Home
  • About
  • No Access
  • Privacy Policy
Bits of .NET
Bits of .NET
  • Asp.Net Core
  • C#
  • SQL
  • JavaScript
  • CSS
  • About
  • ErcanOPAK.com
  • No Access
  • Privacy Policy

Bits of .NET

Daily micro-tips for C#, SQL, performance, and scalable backend engineering.

  • Asp.Net Core
  • C#
  • SQL
  • JavaScript
  • CSS
  • About
  • ErcanOPAK.com
  • No Access
  • Privacy Policy
Ajax

Ajax: Fix a fetch() Call Using keepalive That Silently Gets Capped and Dropped Past 64KB

- 16.10.26 - ErcanOPAK

🔄 The keepalive Request That Got Silently Capped at 64KB

Setting keepalive: true on a fetch() call (the standard way to reliably send analytics or logging data as a page unloads) comes with a strict payload ceiling enforced by the browser – typically a combined 64KB across every pending keepalive request at once. Go over it and the browser doesn’t raise a clear, catchable error specific to the limit – the request is simply never sent, or fails with a generic network error that’s easy to swallow, so the one batch of events most worth keeping (the user’s longest, busiest session) is exactly the one most likely to silently vanish.

🔎 The Problem

window.addEventListener('pagehide', () => {
  const payload = JSON.stringify(collectedEvents);
  // collectedEvents can be large on a long, active session -
  // easily well past 64KB combined with any other pending
  // keepalive request still in flight.
  fetch('/analytics/batch', {
    method: 'POST',
    keepalive: true,
    body: payload,
  });
  // No .catch fires with a specific "payload too large" error -
  // it's simply never sent, and the page is already gone by
  // the time anyone could notice.
});

✅ Fix: Cap or Chunk the Payload Before It Ever Reaches keepalive

  • Measure the serialized payload size client-side and truncate or chunk it to stay comfortably under the combined 64KB limit before setting keepalive: true, rather than discovering the ceiling in production.
  • For anything that isn’t strictly tied to the page unloading, send it earlier with a normal (non-keepalive) fetch that has no size restriction, and reserve keepalive specifically for the small, final summary that must survive the page closing.
  • Add an explicit application-level acknowledgment from the server for critical events, so a silently dropped batch is detectable (missing data on the backend) instead of invisible on both ends.

⚠️ Why This Is Easy to Miss

  • Every test session with a handful of sample events stays safely under the limit, so the code passes every manual check – only a real user’s heaviest, most valuable session is big enough to trigger the drop.
  • There’s no dedicated exception type for this – it either silently never sends or rejects with the same generic error fetch() uses for unrelated network failures, so logging the error tells you almost nothing about the actual cause.

A request marked keepalive is a promise the browser keeps only up to 64KB – past that, the promise quietly expires along with the page.

— Frontend Engineer

Related posts:

Ajax Requests Succeed but Data Is Stale

Ajax Requests Succeed but Data Is Stale

Ajax: Use Axios for HTTP Requests

Ajax: Use Axios for HTTP Requests

AJAX: Use Server-Sent Events for Real-Time Updates Without WebSocket

AJAX: Use Server-Sent Events for Real-Time Updates Without WebSocket

Views: 11

Post navigation

WordPress: Fix a Multisite Subsite That Silently Loses Its Uploaded Media After a Domain Mapping Change
WordPress: Fix a Scheduled Post That Silently Stays in Draft Because WP-Cron Never Actually Fires

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

November 2026
M T W T F S S
 1
2345678
9101112131415
16171819202122
23242526272829
30  
« Oct    

Most Viewed Posts

  • How to make theater mode the default for Youtube (1,055)
  • Get the User Name and Domain Name from an Email Address in SQL (980)
  • How to add default value for Entity Framework migrations for DateTime and Bool (976)
  • Get the First and Last Word from a String or Sentence in SQL (857)
  • How to select distinct rows in a datatable in C# (852)
  • How to enable, disable and check if Service Broker is enabled on a database in SQL Server (653)
  • Add Constraint to SQL Table to ensure email contains @ (607)
  • Average of all values in a column that are not zero in SQL (569)
  • How to use Map Mode for Vertical Scroll Mode in Visual Studio (546)
  • Find numbers with more than two decimal places in SQL (475)

Recent Posts

  • C#: Fix a ConditionalWeakTable Entry Vanishing Too Soon
  • Docker: Fix a Stale COPY Layer After Editing .dockerignore
  • Photoshop: Fix a Pattern Overlay Scaling Wrong on a High-DPI File
  • SQL Server: Fix a Computed Column Index Skipped by Implicit Cast
  • HTML5: Fix a required Input Inside a Hidden Tab Blocking Submit
  • SQL Server: Fix ROW_NUMBER Ties Reordering Between Identical Runs
  • C#: Fix an Enum HasFlag Returning True for the Zero Value
  • WordPress: Fix Featured Images Vanishing After a CDN Migration
  • Photoshop: Fix Content-Aware Fill Smearing a Repeating Pattern
  • Asp.Net Core: Fix Antiforgery Tokens Rejected Behind a Reverse Proxy

Most Viewed Posts

  • How to make theater mode the default for Youtube (1,055)
  • Get the User Name and Domain Name from an Email Address in SQL (980)
  • How to add default value for Entity Framework migrations for DateTime and Bool (976)
  • Get the First and Last Word from a String or Sentence in SQL (857)
  • How to select distinct rows in a datatable in C# (852)

Recent Posts

  • C#: Fix a ConditionalWeakTable Entry Vanishing Too Soon
  • Docker: Fix a Stale COPY Layer After Editing .dockerignore
  • Photoshop: Fix a Pattern Overlay Scaling Wrong on a High-DPI File
  • SQL Server: Fix a Computed Column Index Skipped by Implicit Cast
  • HTML5: Fix a required Input Inside a Hidden Tab Blocking Submit

Social

  • ErcanOPAK.com
  • GoodReads
  • LetterBoxD
  • Linkedin
  • The Blog
  • Twitter
© 2026 Bits of .NET | Built with Xblog Plus free WordPress theme by wpthemespace.com