WHAT PFP WHAT WHAT WHAT

DeathReviews

Why is this an advanced topics now? I didn’t get an alert for that or anything

BigNate469

So, the technical explanation for this:

@codubee maintains Scratch's cache server, meaning they write the code to configure it and generally make sure it's working well. They intentionally programmed that server to, every time their profile picture is requested, send back a random image from a file stored in that server.

If you repeatedly reload the page, you will likely not get a new image each time because your browser decides to use its own cached file instead of requesting it from the server, as a way to save network resources and reduce loading times.

gem1001

BigNate469 wrote:
If you repeatedly reload the page, you will likely not get a new image each time because your browser decides to use its own cached file instead of requesting it from the server, as a way to save network resources and reduce loading times.

It has

cache-control: no-store, max-age=0, s-max-age=0, max-stale=0, min-refresh=0

BigNate469

gem1001 wrote:
BigNate469 wrote:
snip
It has
cache-control: no-store, max-age=0, s-max-age=0, max-stale=0, min-refresh=0

I can only speak from my own experience seeing requests for the picture meet a HTTP 304.

Then again, the last time I tested that was on a Chromebook with fairly strict cache settings because it's a potato, so Chrome might have just ignored that.

It's also possible that it was cached somewhere else along the line.

gem1001

BigNate469 wrote:
I can only speak from my own experience seeing requests for the picture meet a HTTP 304.

Then again, the last time I tested that was on a Chromebook with fairly strict cache settings because it's a potato, so Chrome might have just ignored that.

It's also possible that it was cached somewhere else along the line.

It seems other PFPs only have

cache-control: no-cache

Discuss Scratch