René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"+1 from the W3C TAG","articleBody":"The [W3C Technical Architecture Group (TAG)](https://tag.w3.org) (@w3ctag) is happy to see that the United States government is considering the requirement of encryption and authentication (through use of HTTPS) on all publicly-accessible government Web sites. Doing so will increase the security of people who interact with the government and encourage adoption of a more secure Web, as we documented in the [“Securing the Web” finding](http://www.w3.org/2001/tag/doc/web-https).\n\nA government requirement sends a strong message that encryption and authentication are necessary for Web security, and will encourage government vendors to embrace providing secure services. As has been noted elsewhere, the incremental cost of doing so falling; thanks to efforts like this, we expect it to continue to drop. While good government needs to be cost-conscious, it should not come at the cost of security.\n\nWe note also that where facilities are moved from an http: URL to an https: URL, a redirections should be set up so that existing links do not break. There is ongoing work within the W3C to make this transition easier, and we encourage interested parties to contribute to the [WebAppSec Working Group](http://www.w3.org/2011/webappsec/) and elsewhere.\n\nTim Berners-Lee, @timbl (Chair)\nDaniel Appelquist, @torgo (Chair)\nPeter Linss, @plinss (Chair)\nYves Lafon, @ylafon\nTravis Leithead, @travisleithead\nMark Nottingham, @mnot\nAlex Russell, @slightlyoff\nYan Zhu, @diracdeltas\n","author":{"url":"https://github.com/torgo","@type":"Person","name":"torgo"},"datePublished":"2015-03-30T09:46:43.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/94/https/issues/94"}