Public: anyone can read this; the crew can change it.

A fragment's tag rides in its markup too: Cloudflare strips etag from HTML #324

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

Seen on the live 0.7.42 forge: CSS kept its `etag` through Cloudflare, every HTML fragment lost it, so the conditional fetch never got a 304.

shipped production is serving it deploy d5b2fe2

opened this

Seen on the live 0.7.42 forge: CSS kept its etag through Cloudflare, every HTML fragment lost it, so the conditional fetch never got a 304.

  • layout.fragment stamps the same hash on the fragment's first element as data-etag (of the unstamped body, so the server recomputes it the same way).
  • The client reads the header when it arrives and the attribute when it does not, and sends either back as if-none-match.
  • Test: the stamped attribute equals the header. docs/STUDIO.md says why.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs