Slashdot Mirror
Domain: mnot.net
Stories and comments across the archive that link to mnot.net.
Stories · 3
-
HTTP Error Code 451 Approved For Censored Web Pages (mnot.net)
An anonymous reader writes: The Internet Engineering Steering Group (IESG) has finally approved the new 451 status code for HTTP error messages involving web pages which have been repressed or removed for legal or political reasons. The initiative was proposed in 2013, and gained interest from various groups, such as Lumen (formerly Chilling Effects), who see the potential of the Bradbury-inspired code to help develop comprehensive indexes of censorship on the internet. Mark Nottingham, chair the IETF HTTP Working Group, says, "It'll be an RFC after some work by the RFC Editor and a few more process bits, but effectively you can start using it now." -
HTTP/2 Finalized
An anonymous reader writes: Mark Nottingham, chair of the IETF HTTP working group, has announced that the HTTP/2 specification is done. It's on its way to the RFC Editor, along with the HPACK specification, where it'll be cleaned up and published. "The new standard brings a number of benefits to one of the Web's core technologies, such as faster page loads, longer-lived connections, more items arriving sooner and server push. HTTP/2 uses the same HTTP APIs that developers are familiar with, but offers a number of new features they can adopt. One notable change is that HTTP requests will be 'cheaper' to make. ... With HTTP/2, a new multiplexing feature allows lots of requests to be delivered at the same time, so the page load isn't blocked." Here's the HTTP/2 FAQ, and we recently talked about some common criticisms of the spec. -
HTTP/2 Finalized
An anonymous reader writes: Mark Nottingham, chair of the IETF HTTP working group, has announced that the HTTP/2 specification is done. It's on its way to the RFC Editor, along with the HPACK specification, where it'll be cleaned up and published. "The new standard brings a number of benefits to one of the Web's core technologies, such as faster page loads, longer-lived connections, more items arriving sooner and server push. HTTP/2 uses the same HTTP APIs that developers are familiar with, but offers a number of new features they can adopt. One notable change is that HTTP requests will be 'cheaper' to make. ... With HTTP/2, a new multiplexing feature allows lots of requests to be delivered at the same time, so the page load isn't blocked." Here's the HTTP/2 FAQ, and we recently talked about some common criticisms of the spec.