Rfc 3514

This RFC updates the HTTP/1.1 Media Type from TEXT to MULTICAST because, a

lot, of people request services that are not HTTP/1.1 compliant.

Status of this RFC (version):

This version does not fix the critical behavior of HTTP/1.1:

The Content-Range header cannot be used.

Status of all prior versions (version comments):

Modification date:

Wed May 15 2018. Created by "geeedzegh".
Issued by ICANN.
Go to version details in RFC Editor.
All versions link to a copy in RFC Editor.
+ [RFC 3514] HTTP/1.1 and other headers are defined in the draft https://tools.ietf.org/html/rfc3514.

Authors:

Brendan Gregg, Brian Thompson, Adam Machanic, Andrew Moltz
Fiona Glenanne, Valia Muratova, Jannis Leach, Paola Spindoni
Last Updated: Sun Apr 28 2003. Adapted by "geeedzegh".
Introduction
===========
[RFC 3514](https://tools.ietf.org/html/rfc3514)
in which a new MULTICAST_RANGE in a HTTP header field replaces the HTTP
Content-Range header and causes all requests for services that are not
RRS-compliant to cause them to fail.
There are a couple of use cases that it would be really

useful to support:

- Overhead in the context of embedded APIs that need to poll
through all content sources.
- HTTP PUT, POST, and DELETE for web-based platforms to allow
nested responses and cache optimizations.

Here's why:

1) Any non-HTTP/1.1 compliant request for a web based service to
that cannot be accomplished using a HTTP/1.1 compliant entity
body, will generate an error that the requested service does not
support HTTP. We feel this should be supported.
2) There are a host of interesting entities that do support
HTTP/1.1, like [well known plaintext connections](http://tools.ietf.