Find a Question:
IETF working HTTP 1.1 standard after seven years
The Internet Engineering Task Force has updated the HTTP 1.1 specification. The changes were mainly the specifications of the protocol to clarify and also need to sharpen. Few descriptions
Most importantly RFC2616, a document protocol descriptions that since 1999 served as the basis for HTTP 1.1 is replaced. The reason is that developers started using http for more things than just browsing. To avoid confusion and clarify a few things the Internet Engineering Task Force worked to improve RFC2616.
RFC2616 comprised 176 pages with explanations of definitions, such as get-request management of TCP connections. The specifications are now divided into six parts, so it is easier to read and logically is divided, writes Mark Nottingham chairman of the Task Force.
In total were taken since 2007 include engineers open source organizations and companies such as Google, Microsoft and Apple 550 issues re-examined. All so-called requests for comments, documents which new changes are handled have now been given a section in which the changes are from RFC2616.
Incidentally, not only all documents linguistically cleaned but there are also definitions regarding security issues further tightened. Thus, the folding of several header lines are now obsolete, so HTTP response splitting counter.
President Nottingham late in his blog post finally know that HTTP 2.0 is almost finished and the Internet Engineering Task Force announces more about that soon. That version will partly use the new specification 1.1 and will almost certainly continue standard encryption enabled, it was late last year clearly.Viewing:-165
Answer this Question
You must be Logged In to post an Answer.
Not a member yet? Sign Up Now »
Star Points Scale
Earn points for Asking and Answering Questions!