Diagnosing Turbo Drive full page reloads in Rails
When Turbo Drive falls back to full page reloads, links and forms behave like traditional HTTP navigation. This guide shows how to find the cause and restore partial-page updates.
Loading…
ReadMeFeed / Community knowledge
#turbo-drive
Real questions. Useful conversations. Find the people who know your stack.
Turbo Drive as a Navigation Transport: An Architecture Note for Server-Rendered Apps
Turbo Drive accelerates server-rendered apps by swapping HTML on navigation, but only if the server returns full documents and correct redirects. This note covers the minimal design, trust boundaries, and operational checks.
Turbo Drive fallback limits for silent request failures and client state
Turbo Drive's documented fallback mechanism converts failed Ajax visits into full page loads, but the exact boundary between recoverable and unrecoverable failures remains unclear when requests neither succeed nor explicitly reject. The handbook describes fallback for non-2xx responses and aborted requests, yet the behavior for requests that hang without a r
Turbo Drive request timeouts: no built-in limit for hung visits and form submissions
I'm designing navigation behavior for a Hotwire Turbo application where some endpoints can occasionally hang for a long time. From the documentation, Turbo Drive automatically aborts an in-flight fetch when the user navigates again, and turbo:before-fetch-request lets me intercept or cancel requests. What I cannot find is any documented, built-in network tim
turboTurbo Drive 8 Snapshot Cache: Choosing Header-Based vs Manual Invalidation After Non-GET Submissions
Hotwire apps on Turbo Drive 8.x (with turbo-rails 1.5+) keep a page snapshot cache keyed by URL and scroll position. When a POST, PATCH, or DELETE returns a 2xx response, Turbo does not invalidate the stored snapshot for that URL; invalidation is opt-in via a turbo-cache-control: no-cache response header, a call to Turbo.cache.clear() , or edits inside a tur
