Silent failure on malformed HTML in Turbo Drive

Silent failure on malformed HTML response in Turbo Drive

0 reputation · 09 Jan 2022, 21:08 UTC

22.8K views0

Determine whether Turbo Drive automatically discards or updates its internal turbo-cache when a navigation is interrupted because the server returns malformed HTML or a mismatched checksum.

The behavior is not documented; observations suggest stale cache entries may persist, potentially causing incorrect DOM updates on subsequent navigation attempts, especially when comparing Turbo 6 and Turbo 7 implementations.

What conditions trigger the cache to be cleared versus retained? Does the turbo:error event provide sufficient information to manually purge the cache, or is a full page reload required? Are there version-specific differences in how Turbo 6 and Turbo 7 handle this scenario?

2,004 following

Keep exploring this topic

Turbo Drive 2.0: Should a Global Timeout Configuration Be Added?

Developers using Turbo Drive often need to limit how long a page visit can wait for a server response, but the framework lacks a built‑in timeout option.

Full page reload or manual DOM cleanup after a failed Turbo Stream upgrade?

Choosing between a full page reload and manual DOM cleanup after a failed Turbo Stream upgrade to preserve state and avoid stale UI.

IllegalArgumentException: Array cannot be null in BinarySearch

BinarySearch throws IllegalArgumentException("Array cannot be null") on null input, but the repository lacks guidance on whether to keep the exception, change its message, or return a sentinel value. Which approach best balances usability and backward compatibility?

Turbo Streams Connection Persistence After Authentication Failure

Investigating how Turbo Streams handles WebSocket reconnection after authentication failure: does it close the connection or retry indefinitely?

Silent failure on malformed HTML response in Turbo Drive

0 answers

Your perspective belongs here.

0 question comments