Updated HTTP / 1.1
So unexpectedly, 15 years after the initial publication, the HTTP / 1.1 specification was updated.
There are a lot of updates, I would even say, dofiga. They added a lot of clarifying text, broke the specification at 6 RFCs (it used to be 2), added a new status 308, standardized X-Forwarded-For (now it is just Forward), and much more.
Incomplete list of changes:
New RFCs:
There are a lot of updates, I would even say, dofiga. They added a lot of clarifying text, broke the specification at 6 RFCs (it used to be 2), added a new status 308, standardized X-Forwarded-For (now it is just Forward), and much more.
Incomplete list of changes:
- New status 308 - Permanent Redirect, but with the sending of the same data. Those. The request does not change to GET, as before.
- New Forward header, which is intended to replace X-Forwarded-For and X-Forwarded-Proto
- Removed restriction on 2 server connections
- HTTP 0.9 support removed
- Removed ISO-8859-1 default encoding
- Removed Content-MD5 header
- Disallow use of Content-Range on POST requests
- Added caching of codes 204, 404, 405, 414 and 501
- Changed the documentation of codes 301 and 302 so as to allow redirecting the method from POST to GET. Those. documented the current implementation of all browsers.
- Added distinctions between the ban of referer sending and the case when referer is not present. Now you should send Referer: about: blank if the referer was not.
- Location can now redirect to a link with a hashtag.
New RFCs:
')
Source: https://habr.com/ru/post/225551/
All Articles