Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Screenshot of a portion of firefox dev tools showing the headers of a GET request form x.com. The status is 302 (temporary redirect) and the one response header visible is cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0

Download link

Screenshot of a portion of firefox dev tools showing the headers of a GET request form x.com. The status is 302 (temporary redirect) and the one response header visible is cache-control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0
https://files.mastodon.social/media_attachments/files/112/255/132/968/668/950/original/4eb30d13dfff7b47.png

Notices where this attachment appears

Embed this notice
Reed Mideke (reedmideke@mastodon.social)'s status on Thursday, 21-Nov-2024 06:15:21 JST Reed Mideke
in reply to

Moral of the story, you should never, ever use a 301 without explicitly controlling caching, but vast chunks of the web don't do this (including many registrars "redirect this domain to another site" functionality 😱 ). Anyway, good news for X/twitter is they have not made that particular mistake with x.com

In conversation about a day ago from mastodon.social permalink