Mixing
Why does WordPress use 11 Jan 1984 as an anti-caching value for Expires headers?
The Expires header can be set to a date in the past to prevent caching, although this seems to be regarded as an unusual practice. Any date before today should work for this purpose, but Wordpress uses the very specific date of Wed, 11 Jan 1984 05:00:00 GMT for some reason. I'm pretty sure that WP is the origin of this practice since all discussions involving this date appear to be about WordPress, and this article specifically calls out the Expires header value as a sign of a WordPress server. This blog post remarks upon the unusual date but has nothing very useful to offer about it (unless the cache control headers are meant to honor the death of Fritz Geissler).
It seems to me like it would have been better practice to choose a more generic timestamp like 1 Jan 1900 00:00:00 GMT to avoid surprise at the specificity. It has demonstrably caused some degree of confusion (albeit not much), as can be seen from this forum post. Does anybody know what this date's significance is or why the WordPress developers chose it? I can only assume it's some kind of Easter egg, but it'd be neat to find out the details.
wordpress
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
add a comment |
The Expires header can be set to a date in the past to prevent caching, although this seems to be regarded as an unusual practice. Any date before today should work for this purpose, but Wordpress uses the very specific date of Wed, 11 Jan 1984 05:00:00 GMT for some reason. I'm pretty sure that WP is the origin of this practice since all discussions involving this date appear to be about WordPress, and this article specifically calls out the Expires header value as a sign of a WordPress server. This blog post remarks upon the unusual date but has nothing very useful to offer about it (unless the cache control headers are meant to honor the death of Fritz Geissler).
It seems to me like it would have been better practice to choose a more generic timestamp like 1 Jan 1900 00:00:00 GMT to avoid surprise at the specificity. It has demonstrably caused some degree of confusion (albeit not much), as can be seen from this forum post. Does anybody know what this date's significance is or why the WordPress developers chose it? I can only assume it's some kind of Easter egg, but it'd be neat to find out the details.
wordpress
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
1
Maybe it's a birthday, or a date special to one of the original coders? So, "Easter egg".
– user2864740
Jan 2 at 20:30
add a comment |
The Expires header can be set to a date in the past to prevent caching, although this seems to be regarded as an unusual practice. Any date before today should work for this purpose, but Wordpress uses the very specific date of Wed, 11 Jan 1984 05:00:00 GMT for some reason. I'm pretty sure that WP is the origin of this practice since all discussions involving this date appear to be about WordPress, and this article specifically calls out the Expires header value as a sign of a WordPress server. This blog post remarks upon the unusual date but has nothing very useful to offer about it (unless the cache control headers are meant to honor the death of Fritz Geissler).
It seems to me like it would have been better practice to choose a more generic timestamp like 1 Jan 1900 00:00:00 GMT to avoid surprise at the specificity. It has demonstrably caused some degree of confusion (albeit not much), as can be seen from this forum post. Does anybody know what this date's significance is or why the WordPress developers chose it? I can only assume it's some kind of Easter egg, but it'd be neat to find out the details.
wordpress
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
The Expires header can be set to a date in the past to prevent caching, although this seems to be regarded as an unusual practice. Any date before today should work for this purpose, but Wordpress uses the very specific date of Wed, 11 Jan 1984 05:00:00 GMT for some reason. I'm pretty sure that WP is the origin of this practice since all discussions involving this date appear to be about WordPress, and this article specifically calls out the Expires header value as a sign of a WordPress server. This blog post remarks upon the unusual date but has nothing very useful to offer about it (unless the cache control headers are meant to honor the death of Fritz Geissler).
It seems to me like it would have been better practice to choose a more generic timestamp like 1 Jan 1900 00:00:00 GMT to avoid surprise at the specificity. It has demonstrably caused some degree of confusion (albeit not much), as can be seen from this forum post. Does anybody know what this date's significance is or why the WordPress developers chose it? I can only assume it's some kind of Easter egg, but it'd be neat to find out the details.
wordpress
wordpress
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
asked Jan 2 at 20:29
HydrothermalHydrothermal
2,25871737
2,25871737
1
Maybe it's a birthday, or a date special to one of the original coders? So, "Easter egg".
– user2864740
Jan 2 at 20:30
add a comment |
1
Maybe it's a birthday, or a date special to one of the original coders? So, "Easter egg".
– user2864740
Jan 2 at 20:30
1
1
Maybe it's a birthday, or a date special to one of the original coders? So, "Easter egg".
– user2864740
Jan 2 at 20:30
Maybe it's a birthday, or a date special to one of the original coders? So, "Easter egg".
– user2864740
Jan 2 at 20:30
add a comment |
1 Answer
1
active
oldest
votes
Looks like this goes back to WordPress version 2.1.
Doing a bit of digging, the first use of this date in a functions.php was in commit 2623, where it was used in the nocache_headers() function.
Prior to that, it had been copied & pasted around a few times. I think the first instance of this was commit 1983, where the non-cachable date in one case was changed from the birthdate of "Michel" (maybe Michel Valdrighi?) to the 1984 date. The message on that commit is:
Don't cache. No, really. Hat tip: Kimmo Suominen.
That commit came from Matt Mullenweg, whose birthday is listed as 11 January 1984 by Wikipedia.
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
Great digging! Thanks for the research.
– Hydrothermal
Jan 2 at 21:41
add a comment |
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%2f54012749%2fwhy-does-wordpress-use-11-jan-1984-as-an-anti-caching-value-for-expires-headers%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Looks like this goes back to WordPress version 2.1.
Doing a bit of digging, the first use of this date in a functions.php was in commit 2623, where it was used in the nocache_headers() function.
Prior to that, it had been copied & pasted around a few times. I think the first instance of this was commit 1983, where the non-cachable date in one case was changed from the birthdate of "Michel" (maybe Michel Valdrighi?) to the 1984 date. The message on that commit is:
Don't cache. No, really. Hat tip: Kimmo Suominen.
That commit came from Matt Mullenweg, whose birthday is listed as 11 January 1984 by Wikipedia.
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
Great digging! Thanks for the research.
– Hydrothermal
Jan 2 at 21:41
add a comment |
Looks like this goes back to WordPress version 2.1.
Doing a bit of digging, the first use of this date in a functions.php was in commit 2623, where it was used in the nocache_headers() function.
Prior to that, it had been copied & pasted around a few times. I think the first instance of this was commit 1983, where the non-cachable date in one case was changed from the birthdate of "Michel" (maybe Michel Valdrighi?) to the 1984 date. The message on that commit is:
Don't cache. No, really. Hat tip: Kimmo Suominen.
That commit came from Matt Mullenweg, whose birthday is listed as 11 January 1984 by Wikipedia.
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
Great digging! Thanks for the research.
– Hydrothermal
Jan 2 at 21:41
add a comment |
Looks like this goes back to WordPress version 2.1.
Doing a bit of digging, the first use of this date in a functions.php was in commit 2623, where it was used in the nocache_headers() function.
Prior to that, it had been copied & pasted around a few times. I think the first instance of this was commit 1983, where the non-cachable date in one case was changed from the birthdate of "Michel" (maybe Michel Valdrighi?) to the 1984 date. The message on that commit is:
Don't cache. No, really. Hat tip: Kimmo Suominen.
That commit came from Matt Mullenweg, whose birthday is listed as 11 January 1984 by Wikipedia.
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
Looks like this goes back to WordPress version 2.1.
Doing a bit of digging, the first use of this date in a functions.php was in commit 2623, where it was used in the nocache_headers() function.
Prior to that, it had been copied & pasted around a few times. I think the first instance of this was commit 1983, where the non-cachable date in one case was changed from the birthdate of "Michel" (maybe Michel Valdrighi?) to the 1984 date. The message on that commit is:
Don't cache. No, really. Hat tip: Kimmo Suominen.
That commit came from Matt Mullenweg, whose birthday is listed as 11 January 1984 by Wikipedia.
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
answered Jan 2 at 21:34
s3cur3s3cur3
8781824
8781824
Great digging! Thanks for the research.
– Hydrothermal
Jan 2 at 21:41
add a comment |
Great digging! Thanks for the research.
– Hydrothermal
Jan 2 at 21:41
Great digging! Thanks for the research.
– Hydrothermal
Jan 2 at 21:41
Great digging! Thanks for the research.
– Hydrothermal
Jan 2 at 21:41
add a comment |
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%2f54012749%2fwhy-does-wordpress-use-11-jan-1984-as-an-anti-caching-value-for-expires-headers%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
1
Maybe it's a birthday, or a date special to one of the original coders? So, "Easter egg".
– user2864740
Jan 2 at 20:30