undefined | Better HN

0 pointsnewman31414y ago0 comments

Plus if you access Twitter over SSL, there might not be caching resulting in heavy loads repeatedly.

0 comments

ceejayoz14y ago

I'd imagine Twitter's serving `Cache-Control: public` where appropriate.

newman314OP14y ago

You would think but sadly, no.

They serve the actual tweet as "Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0"

https://pastee.org/bzeb5

EDIT: Just to check, I also looked at one of their css resources. https://si0.twimg.com/a/1330626450/t1/css/t1_core_logged_out...

Cache-Control: private, max-age=31449600

So I'm not confident Twitter actually understands how to set things.

PS: Hey Twitter, I can help =)

eonwe14y ago

Maybe it's just that they don't want that one page cached as they may update their scripts, images and stylesheets. And for that css-file, I think that whenever they change the css, they'll just give the resource a new address so cache is only invalidated when there are actual changes.

1 more reply

j / k navigate · click thread line to collapse