Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gui: Be more explicit about how assets should be cached (fixes #3182) #3221

Closed
wants to merge 1 commit into from

Conversation

canton7
Copy link
Member

@canton7 canton7 commented May 30, 2016

Purpose

With the previous setup, browsers were free to use a local cache for any
length of time they pleased: we didn't set an 'Expires' header (or
max-age directive), and Cache-Control just said "you're free to cache
this".

Therefore be more explicit: we don't mind if browsers cache things, but
they MUST revalidate everything on every request.

Testing

Set STTRACE=http, reloaded lots in some browsers, saw that browsers always revalidated.

…ing#3182)

With the previous setup, browsers were free to use a local cache for any
length of time they pleased: we didn't set an 'Expires' header (or
max-age directive), and Cache-Control just said "you're free to cache
this".

Therefore be more explicit: we don't mind if browsers cache things, but
they MUST revalidate everything on every request.
@AudriusButkevicius
Copy link
Member

AudriusButkevicius commented May 30, 2016

LGTM, leave for @calmh to merge.

@calmh
Copy link
Member

calmh commented May 30, 2016

@st-review merge please

cmd/syncthing: Be more explicit about how assets should be cached (fixes #3182)

With the previous setup, browsers were free to use a local cache for any
length of time they pleased: we didn't set an 'Expires' header (or
max-age directive), and Cache-Control just said "you're free to cache
this".

Therefore be more explicit: we don't mind if browsers cache things, but
they MUST revalidate everything on every request.

@st-review
Copy link

👌 Merged as 6361172. Thanks, @canton7!

@st-review st-review closed this May 30, 2016
st-review pushed a commit that referenced this pull request May 30, 2016
 #3182)

With the previous setup, browsers were free to use a local cache for any
length of time they pleased: we didn't set an 'Expires' header (or max-age
directive), and Cache-Control just said "you're free to cache this".

Therefore be more explicit: we don't mind if browsers cache things, but they
MUST revalidate everything on every request.

GitHub-Pull-Request: #3221
@st-review st-review added the frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion label Jun 16, 2017
@syncthing syncthing locked and limited conversation to collaborators Jun 16, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
frozen-due-to-age Issues closed and untouched for a long time, together with being locked for discussion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants