Editing Talk:1854: Refresh Types
Please sign your posts with ~~~~ |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
<!--Please sign your posts with ~~~~ and not delete this comment.--> | <!--Please sign your posts with ~~~~ and not delete this comment.--> | ||
− | |||
− | |||
Similar to [https://xkcd.com/1638/ this comic]. [[Special:Contributions/108.162.212.83|108.162.212.83]] 14:55, 23 June 2017 (UTC) | Similar to [https://xkcd.com/1638/ this comic]. [[Special:Contributions/108.162.212.83|108.162.212.83]] 14:55, 23 June 2017 (UTC) | ||
Line 69: | Line 67: | ||
"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." | "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. | + | 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. |
− | |||
− | |||
− |