Datasette catches a pagination header causing extra browser requests
Simon Willison found Firefox fetching the next table page automatically because Datasette sent an HTTP Link header with rel="next". In his example, opening one table triggered roughly 80 KB of additional HTML and an unnecessary server request. Datasette closed the issue with a change removing that header for HTML pages, illustrating how pagination metadata can also affect browser network behavior.
Simon Willison · Datasette · Nov 7, 2026
Why it matters
Unexpected background requests may come from response headers rather than visible JavaScript or user actions.
More context
Inspect the browser network panel alongside response headers when tracing duplicate page work. The linked issue records the finding and a completed source change; check your installed Datasette release before assuming that change is present in a deployed service.
Keep in mind
The report concerns Firefox’s prefetch behavior for this header and an observed table response; it does not establish equivalent behavior in every browser.
Original read