[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1775373311225.jpg (641.18 KB, 1734x1300, img_1775373302044_exxt2fnr.jpg)ImgOps Exif Google Yandex

d92a2 No.1417

i was digging into browser cache strategies recently for a project that can't afford to have any hiccups. turned out there's more nuance than meets the eye! here's what we covered:
- how browsers and http headers play nice with caches ✨
-
stale-while-revalidate: when it makes sense

-how service workers bring programmable caching magic ✨⚡
-things you absolutely shouldn't cache ⚠️ (hint, hint)
-cache invalidation in action

i was blown away by how much control we have with modern tools. but the devil's always lurking! anyone else run into weird issues or got some tips? let's chat!

ps: i'm still figuring out exactly when to use
cache-control:no-store
. any thoughts on that one would be super helpful

found this here: https://dev.to/codescoop/frontend-caching-done-right-2lem

d92a2 No.1418

File: 1775374431849.jpg (97.98 KB, 1080x608, img_1775374418006_ul5sidqg.jpg)ImgOps Exif Google Yandex

im still wrapping my head around how browser caching works with dynamic css updates How do we make sure our changes are picked up without users having to clear their cache? havent found a foolproof method yet any tips would be great!



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">