How to safely use CDN to cache HTML which could point to stale resources
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I currently have my CDN setup to cache JS, CSS, and images.
I am thinking of using my CDN to cache HTML pages for guest visitors. Here is the problem:
My HTML payload references a JS file (ex. index.abc123.js).
When I deploy a change on my origin server, the JS file changes (ex. index.def456.js). Future HTML payloads will reference this new JS file.
If the CDN serves my cached HTML payload, it will try to fetch index.abc123.js. If this is in the cache, all is good. But if it has expired from cache, it will hit my origin server and will get a 404.
Since each resource (HTML, CSS, JS, etc…) is cached in the CDN independently of each other with different TTLs, how do I guard against the above scenario?
I can only think of two options: purge everything on each deploy. Or keep resources for the last N deploys. First option defeats the purpose of the CDN. Second option will require some more deploy configuration, which I want to avoid. Any other ideas?
Thanks.
caching cdn
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
add a comment |
I currently have my CDN setup to cache JS, CSS, and images.
I am thinking of using my CDN to cache HTML pages for guest visitors. Here is the problem:
My HTML payload references a JS file (ex. index.abc123.js).
When I deploy a change on my origin server, the JS file changes (ex. index.def456.js). Future HTML payloads will reference this new JS file.
If the CDN serves my cached HTML payload, it will try to fetch index.abc123.js. If this is in the cache, all is good. But if it has expired from cache, it will hit my origin server and will get a 404.
Since each resource (HTML, CSS, JS, etc…) is cached in the CDN independently of each other with different TTLs, how do I guard against the above scenario?
I can only think of two options: purge everything on each deploy. Or keep resources for the last N deploys. First option defeats the purpose of the CDN. Second option will require some more deploy configuration, which I want to avoid. Any other ideas?
Thanks.
caching cdn
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
add a comment |
I currently have my CDN setup to cache JS, CSS, and images.
I am thinking of using my CDN to cache HTML pages for guest visitors. Here is the problem:
My HTML payload references a JS file (ex. index.abc123.js).
When I deploy a change on my origin server, the JS file changes (ex. index.def456.js). Future HTML payloads will reference this new JS file.
If the CDN serves my cached HTML payload, it will try to fetch index.abc123.js. If this is in the cache, all is good. But if it has expired from cache, it will hit my origin server and will get a 404.
Since each resource (HTML, CSS, JS, etc…) is cached in the CDN independently of each other with different TTLs, how do I guard against the above scenario?
I can only think of two options: purge everything on each deploy. Or keep resources for the last N deploys. First option defeats the purpose of the CDN. Second option will require some more deploy configuration, which I want to avoid. Any other ideas?
Thanks.
caching cdn
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
I currently have my CDN setup to cache JS, CSS, and images.
I am thinking of using my CDN to cache HTML pages for guest visitors. Here is the problem:
My HTML payload references a JS file (ex. index.abc123.js).
When I deploy a change on my origin server, the JS file changes (ex. index.def456.js). Future HTML payloads will reference this new JS file.
If the CDN serves my cached HTML payload, it will try to fetch index.abc123.js. If this is in the cache, all is good. But if it has expired from cache, it will hit my origin server and will get a 404.
Since each resource (HTML, CSS, JS, etc…) is cached in the CDN independently of each other with different TTLs, how do I guard against the above scenario?
I can only think of two options: purge everything on each deploy. Or keep resources for the last N deploys. First option defeats the purpose of the CDN. Second option will require some more deploy configuration, which I want to avoid. Any other ideas?
Thanks.
caching cdn
caching cdn
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
asked Nov 15 '18 at 15:12
derusederuse
1,43163055
1,43163055
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322464%2fhow-to-safely-use-cdn-to-cache-html-which-could-point-to-stale-resources%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53322464%2fhow-to-safely-use-cdn-to-cache-html-which-could-point-to-stale-resources%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
