Source: https://trac.ietf.org/trac/httpbis/browser/draft-ietf-httpbis/00/draft-ietf-httpbis-p2-semantics-00.xml?rev=798
Timestamp: 2020-01-19 01:23:04
Document Index: 798252901

Matched Legal Cases: ['art3', 'art3', 'art3', 'art7', 'art4', 'art4', 'art4', 'art5', 'art4', 'art7', 'art5', 'art6', 'art4', 'art7', 'art6', 'art7', 'art1', 'art1', 'art1']

draft-ietf-httpbis-p2-semantics-00.xml in draft-ietf-httpbis/00 – Hypertext Transfer Protocol Wiki
source: draft-ietf-httpbis/00/draft-ietf-httpbis-p2-semantics-00.xml @ 798
Last change on this file since 798 was 67, checked in by julian.reschke@…, 12 years ago
<rfc obsoletes="2068, 2616" category="std" ipr="full3978" docName="draft-ietf-httpbis-p2-semantics-00">
<figure><iref primary="true" item="Grammar" subitem="product"/><iref primary="true" item="Grammar" subitem="product-version"/><artwork type="abnf2616"><![CDATA[
Product tokens SHOULD be short and to the point. They MUST NOT be
token character MAY appear in a product-version, this token SHOULD
the same product SHOULD only differ in the product-version portion of
Method = "OPTIONS" ; Section 8.2
| "GET" ; Section 8.3
| "HEAD" ; Section 8.4
| "POST" ; Section 8.5
| "PUT" ; Section 8.6
| "DELETE" ; Section 8.7
| "TRACE" ; Section 8.8
| "CONNECT" ; Section 8.9
| Accept-Charset ; [Part3], Section 5.2
| Accept-Encoding ; [Part3], Section 5.3
| Accept-Language ; [Part3], Section 5.4
| Authorization ; [Part7], Section 3.1
| If-Match ; [Part4], Section 6.2
| If-Modified-Since ; [Part4], Section 6.3
| If-None-Match ; [Part4], Section 6.4
| If-Range ; [Part5], Section 5.3
| If-Unmodified-Since ; [Part4], Section 6.5
| Proxy-Authorization ; [Part7], Section 3.3
| Range ; [Part5], Section 5.4
| Age ; [Part6], Section 3.1
| ETag ; [Part4], Section 6.1
| Proxy-Authenticate ; [Part7], Section 3.2
| Vary ; [Part6], Section 3.5
| WWW-Authenticate ; [Part7], Section 3.4
The Host request-header field (Section 8.4 of <xref target="Part1"/>) MUST accompany all
extension MAY discard the request body.
POST requests MUST obey the message transmission requirements set out
in Section 7.2 of <xref target="Part1"/>.
new resource is created, the origin server MUST inform the user agent
PUT requests MUST obey the message transmission requirements set out
"message/http". Responses to this method MUST NOT be cached.
than GET or HEAD, the user agent MUST NOT automatically redirect the
SHOULD be retrieved using a GET method on that resource. This method
response MUST NOT be cached, but the response to the second
The different URI SHOULD be given by the Location field in the
The requested resource MUST be accessed through the proxy given by
proxy. 305 responses MUST only be generated by origin servers.
SHOULD be followed. The actual set of allowed methods is defined
The Allow header field MAY be provided with a PUT request to
SHOULD include an Allow header in the response giving the actual
SHOULD include a Via field (as described in Section 8.9 of <xref target="Part1"/>).
Authors of services which use the HTTP protocol SHOULD NOT use GET
<seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p3-payload-00"/>
<seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-00"/>