Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

HTTP/2 is now utterly officially official

RFC published and there's no going back from that without getting out the engraving gear

HTTP/2 was signed off back in February, but the spec took its final step towards becoming a standard on Thursday US time with the publication of rfc7540.

RFCs - request for comments - are counterintuitively named because as the Internet Engineering Task Force explains, “Once an RFC is published, it is never revised. If the specification it describes changes, the standard will be re-published in another RFC that "obsoletes" the first.”

HTTP appearing at ref-editor.org (the second link in this story) therefore means the definitive version of the standard has now been chiselled into stone and set down before the people to gaze upon in awe and obedient wonder.

Now that the spec is utterly, officially official, web server upgrades beckon. Internet Information Server is already compliant. Apache has planned an add-on and nginix has pledged to get it working by the end of 2015. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like