{"id":31068,"date":"2017-07-01T03:01:43","date_gmt":"2017-06-30T17:01:43","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=31068"},"modified":"2017-08-11T18:22:29","modified_gmt":"2017-08-11T08:22:29","slug":"webpage-that-self-destructs-primer-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/webpage-that-self-destructs-primer-tutorial\/","title":{"rendered":"Webpage that Self-Destructs Primer Tutorial"},"content":{"rendered":"
\"Webpage<\/a>

Webpage that Self-Destructs Primer Tutorial<\/p><\/div>\n

You’d probably have heard of the mobile app Snapchat<\/a> and perhaps the principles of how it works<\/a>.<\/p>\n

This design reminds me of that Mission Impossible “This tape will self-destruct”<\/a> modus operandi. So, today, we set out using PHP to have a webpage be created by a user with their own textual content, that will exist on the rjmprogramming.com.au web server for up to three minutes before self destructing. The user can know this, or test this, by clicking a link labelled “own content” on this webpage they’ve created, and for up to three minutes that will not cause a web server 404<\/a> (not found) error, but then the webpage self-destructs. Or appears to anyway. The thing is, the HTML that is your webpage cannot achieve this even if it wanted too, but back when the user created that HTML webpage (perhaps with their own content) “destiny” had already set the wheels in motion to have that webpage be removed from the web server, with a combination of PHP functionalities, that go …<\/p>\n