Title text: The hardest refresh requires both a Mac keyboard and a Windows keyboard as a security measure, like how missile launch systems require two keys to be turned at once.
|| This explanation may be incomplete or incorrect: This is chaos - multiple explanations should be merged and condensed. Do NOT delete this tag too soon.|
If you can address this issue, please edit the page! Thanks.
This Comic lists five different levels of refresh operations for web applications. The first three (soft, normal, and hard refresh) are different operations done in the browser to request that information be retrieved from the server. The other two (harder and hardest refresh) are further, imaginary operations that perform "refresh" operations on remote resources.
A "normal refresh" is a browser operation that reloads portions of a web page that have changed since the original load. It is the refresh operation triggered by refresh buttons in browsers, though can also be activated using the three common keyboard commands listed by Randall, and will generally accomplish the same thing as a soft refresh, with the additional cost of reloading the web page.
Hard refresh is a less common browser operation that clears any cached files associated with the page before requesting a new copy. Browser caching is a way to store webpage resources locally in order to decrease load time and data transmitted. Hard refreshes are usually used when a webapp has changed in such a way that the cached data is interfering with the proper display of the page. A hard refresh is slower because it forces the browser to download the entire page, but it ensures that the page is displayed as it is currently being served.
Interestingly, hard refresh HTTP request contains special headers (associated metadata) that command all intermediate proxy servers to drop their caches too. These headers can be seen by end application running on the web server, that can choose to reload some data from database and redo some long-running calculations in this case, even though this is not mandated by HTTP standard. In orchestrated environment it may indirectly cause some virtual machines to be rebooted. Rebooting actual physical server upon web page hard refresh is of course not normal, but additional processing may trigger some hardware or operating system bug that will cause exactly this.
"Harder refresh" is a joke that extends the existing naming scheme. The joke is that if a "hard refresh" resets the browser display and cache, a harder refresh should reset the source of the data by cycling power in the data center. Assuming no damage was done, this would reset the memory on the server, erasing any information that had not been written to disk, and setting the server to the state it was in at launch. This would cause considerable downtime, and would be unlikely to help the user at all.
The fifth option, "hardest refresh", moves beyond resetting the source of the data and resets the entire internet back to ARPANET, an early military network which was a forerunner to the modern internet. The implications of this are not made clear, but it should be noted that it wouldn't help to fix any problems a user is experiencing in-browser, as HTTP, the protocol by which web pages are sent, was not developed until late 1990, the year ARPANET was decommissioned.
The Keyboard shortcuts listed for the three real actions are, in fact, standard shortcuts. shortcuts tend to be longer and more complicated for less common operations, and the fake shortcuts play to this idea. The "harder refresh" uses six keys, including the non-standard 'HYPER' key, a feature of the Space cadet keyboard.
The "hardest refresh" shortcut uses fifteen keys, including non-standard ones such as Ø and ⏏. (The latter is the "eject" key found on [older?] Mac keyboards.) The shortcut makes amusing comparisons about a shortcut that includes not only the F5 function key, but also the keys for the letter "F" and the digit "5", as well as the similarity in appearance between O, 0, and Ø.
The title text suggests that the inclusion of both the windows key and command key in the "Hardest refresh" shortcut is a security measure akin to the Two-man rule, as it would require two keyboards to enter.
|| This transcript is incomplete. Please help editing it! Thanks.
| Refresh Type
|| Example Shortcuts
| Soft Refresh
|| Gmail REFRESH Button
| Normal Refresh
|| F5, CTRL-R, ⌘-R
|| CTRL-F5, CTRL-⇧, ⌘-⇧-R
|| Refreshes page including cached files
|| Remotely cycles power to datacenter
||CTRL- ⌘⊞⇧#-R-F5-F-5-ESC-O-0-Ø-⏏-SCROLL LOCK
||Internet starts over from Arpanet
add a comment! ⋅ add a topic (use sparingly)! ⋅ refresh comments!
Similar to this comic. 184.108.40.206 14:55, 23 June 2017 (UTC)
Aren't you supposed to use Shift-F5 (at least in chrome) for a hard refresh - not Ctrl - F5. https://support.google.com/chrome/answer/157179?visit_id=1-636338263045956762-2405452703&hl=en&rd=2 220.127.116.11 (talk) (please sign your comments with ~~~~)
- I believe that's correct. It is likely browser dependent. --Arccos (talk) 15:27, 23 June 2017 (UTC)
- Erratum: The middle hard-refresh option is missing something - it lists only modifier keys. 18.104.22.168 15:32, 23 June 2017 (UTC)
- It appears that the "hard refresh" option is a real option, but that the keyboard shortcuts in the comic may not be correct. The above user's linked material suggests that the keyboard shortcut for a hard refresh, labeled "Reload the current page, ignoring cached content", is, in Chrome, SHIFT-F5 or CTRL-Shift-R on Windows and APPLE-Shift-R on a keyboard for MacOS. This is in contrast to the comic, which currently lists CTRL-F5, CTRL-Up, and APPLE-UP-R as the shortcuts. 22.214.171.124 15:33, 23 June 2017 (UTC)
- That's not an "UP," the symbol ⇧ represents the SHIFT key. Indeed it appears Randall omitted the 'R' inadvertently. JohnHawkinson (talk) 15:46, 23 June 2017 (UTC)
- Randall says the keys are examples, meaning some may missing. But for me it looks like the most common shortcuts. Except the hard refresh by pressing CTRL+SHIFT, that's nonsense because a F5 or R should follow. I'm sure we will see a picture update soon. Stay tuned...--Dgbrt (talk) 15:44, 23 June 2017 (UTC)
- Ctrl-F5 works across every browser. It does appear that Shift-F5 also works in Chrome. Trlkly (talk) 23:35, 23 June 2017 (UTC)
The missile launch keys can be totally identical for the two-man rule to work; the thing is not that they are interchangeable, but that the locks are too far apart for one person to operate both. Chrullrich (talk) 18:49, 23 June 2017 (UTC)
- Big Bang refresh - restarts universe just to be sure there's nothing stuck in cache. (Of course in EMACS, that's just good old: C-x M-c M-bigbang). :-) 126.96.36.199 20:41, 23 June 2017 (UTC)
It looks like the "harder refresh" shortcut also requires two keyboards to work, since the "hyper" key seems to only exist on the space-cadet keyboard, which does not have an F5 key. 188.8.131.52 19:12, 23 June 2017 (UTC)
What do we use when Skynet takes over? OldCorps (talk) 19:33, 23 June 2017 (UTC)
Gmail does not update instantaneously at all. I don't know how many times I've gotten a notification from my RSS feed, and then have to go to Gmail and press refresh. And that's not even counting external email. I frequently use the Gmail refresh button. Trlkly (talk) 23:30, 23 June 2017 (UTC)
- That's weird, it definitely does for me. Sometimes it'll even update with the new unread emails before I get a notification that I got a new email. It updates faster than my work email. OldCorps (talk) 10:35, 24 June 2017 (UTC)
I also find it funny that this page uses an additional type of refresh: the "purge server cache" kind. Trlkly (talk) 23:30, 23 June 2017 (UTC)
Powercycling datacenter can't be that long downtime unless the servers starts checking discs. And sometimes remotely triggering soft reset of server would really help user of incorrectly written application - servers are generally configured in way which allows them to start all needed services automatically. -- Hkmaly (talk) 23:47, 23 June 2017 (UTC)
Dear Dgbrt, before deleting things and writing on topic you don't know about, please at least read this, this and this. 184.108.40.206 (talk) (please sign your comments with ~~~~)
- Hi IP, please sign your posts with ~~~~.
- I have mentioned RFC 7234 meta-tags for suppressing caching.
- "Difference between Ctrl+Refresh and Ctrl+Shift+Refresh". This an old QA from 2009 and still browser dependent. The HTTP-Response "304 Not Modified" isn't always reliable as I also have mentioned.
- Your reboot statement doesn't belong to any cache issues. I will move it to the harder refresh section.
- Please stop the edit war by just undoing content. I have rewritten something by using many existing phrases. Please read my edits first before becoming upset. And please follow a unique style according to the rest of the page.--Dgbrt (talk) 10:44, 24 June 2017 (UTC)
- No war. I am clearly bad at explaining, so I'll not touch this explanation any more; you are free to fix it the way you want. But at least investigate the issue first, since your proposed sentence showed that you are not familiar with the issue. 220.127.116.11 (talk) (please sign your comments with ~~~~)
- Hi IP, PLEASE sign your posts with ~~~~.
- I'm a web developer for more than 20 years including mobile devices as clients at a time the word smartphone wasn't invented. My 2ct.--Dgbrt (talk) 11:28, 25 June 2017 (UTC)
- Status - currently eating popcorn waiting for the response to the haymaker Dgbrt just delivered. OldCorps (talk) 12:06, 25 June 2017 (UTC)
- Off-topic transcript discussion
I want to say that ELinks (the text-based web browser that I, for some reason, have on my Ubuntu) displays this for the talk section. Isn't the transcript for text-based web browsers on comics where the official transcript fails? Also, I can't figure out how to put headers in. JacobDS65536 (talk) 01:33, 24 June 2017 (UTC)
- I don't understand your problem. Are you talking about the talk section or the transcript? And what's wrong except the inverse text?--Dgbrt (talk) 10:44, 24 June 2017 (UTC)
- The discussion area is enclosed in a div tag with some sort of background and text color settings. Your copy of ELinks is probably trying to emulate the background for you. --18.104.22.168 02:25, 25 June 2017 (UTC)
Seems like Randall keeps returning to missile launch topics after Trump... There have been quite a few since then. --Kynde (talk) 13:57, 24 June 2017 (UTC)
- He mentioned the nuclear briefcase back during the Obama administration. 22.214.171.124 16:09, 24 June 2017 (UTC)
It would be nice if the transcript section here would use words to describe what the symbols are. Or possibly a separate table in the explanation section. Thanks 126.96.36.199 23:49, 24 June 2017 (UTC)
- That's the reason why it's still incomplete. A real transcript doesn't need a table but a description what's in the image. This includes the full text but also a description of the content like pictures or symbols.--Dgbrt (talk) 11:28, 25 June 2017 (UTC)
Looks like Randall missed out a couple of intermediate refreshes:
- Service refresh: restarts the HTTPD service on the web server, clearing out the services's cache
- Warm server reboot: restarts the OS on the web server, clearing out the OS's cache
The cold server reboot usually clears out hardware caches, but the cache of battery-backed RAID controllers will survive a cold reboot.
--188.8.131.52 10:34, 25 June 2017 (UTC)
- Hey, you are on the server side. ;) --Dgbrt (talk) 11:28, 25 June 2017 (UTC)
So, what type of refresh are you all using today to make the next comic appear on xkcd? :-) 184.108.40.206 11:29, 26 June 2017 (UTC)
I think part of the joke is also that harder/hardest refers to the difficulty of using those shortcuts, instead of just the implications of the refresh command. --220.127.116.11 14:22, 26 June 2017 (UTC)
"And rebooting an actual physical server upon a web page request is not possible, unless there is a software or operating system bug that will cause exactly this."
This is not exactly correct. It would be very possible to write functionality into a webpage (deliberately; not a bug) to reboot the server that it is running on or another server. This functionality would need server credentials to do so, provided by either the web coder or the user. This would be useful in e.g. a cloud infrastructure management dashboard. It would be a very bad idea to a public facing webpage without credentials required to prove that the user is authorized to perform reboots of the given servers. 18.104.22.168 (talk) (please sign your comments with ~~~~)
- Maybe it should read "common web pages" or something similar, because you're right. There are administrative web pages like Webmin capable of doing exactly this.--Dgbrt (talk) 17:02, 26 June 2017 (UTC)
Somehow, somewhere, I was expecting a reference to the Konami code for the Hardest Refresh. :) (i.e. either by Randall or somewhere here) NiceGuy1 (talk) 04:52, 27 June 2017 (UTC)