Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Rough in discussion of extensibility#384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
mnot merged 13 commits intomasterfrommnot-44
Jul 9, 2020
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletionsdraft-ietf-httpbis-cache-latest.xml
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -1218,7 +1218,6 @@
</tbody>
</table>
<!--(END)-->

<?ENDINC build/draft-ietf-httpbis-cache-latest.iana-headers ?>

<section title="Age" anchor="field.age">
Expand DownExpand Up@@ -1381,7 +1380,6 @@
</tbody>
</table>
<!--(END)-->

<?ENDINC build/draft-ietf-httpbis-cache-latest.cache-directives ?>

<section title="Request Cache-Control Directives" anchor="cache-request-directive">
Expand DownExpand Up@@ -2343,19 +2341,19 @@

<x:ref>Expires</x:ref> = HTTP-date

<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, see <xref target="Semantics" x:fmt="," x:sec="10.1.1.1"/>&gt;
<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, see <xref target="Semantics" x:fmt="," x:sec="11.1.1.1"/>&gt;

<x:ref>OWS</x:ref> = &lt;OWS, see <xref target="Semantics" x:fmt="," x:sec="1.2.1"/>&gt;

<x:ref>cache-directive</x:ref> = token [ "=" ( token / quoted-string ) ]

<x:ref>delta-seconds</x:ref> = 1*DIGIT

<x:ref>field-name</x:ref> = &lt;field-name, see <xref target="Semantics" x:fmt="," x:sec="4.3"/>&gt;
<x:ref>field-name</x:ref> = &lt;field-name, see <xref target="Semantics" x:fmt="," x:sec="5.3"/>&gt;

<x:ref>quoted-string</x:ref> = &lt;quoted-string, see <xref target="Semantics" x:fmt="," x:sec="4.4.1.2"/>&gt;
<x:ref>quoted-string</x:ref> = &lt;quoted-string, see <xref target="Semantics" x:fmt="," x:sec="5.4.1.2"/>&gt;

<x:ref>token</x:ref> = &lt;token, see <xref target="Semantics" x:fmt="," x:sec="4.4.1.1"/>&gt;
<x:ref>token</x:ref> = &lt;token, see <xref target="Semantics" x:fmt="," x:sec="5.4.1.1"/>&gt;
</sourcecode>
</section>
<?ENDINC build/draft-ietf-httpbis-cache-latest.abnf-appendix ?>
Expand Down
13 changes: 6 additions & 7 deletionsdraft-ietf-httpbis-messaging-latest.xml
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -863,7 +863,6 @@ https://www.example.org
</tbody>
</table>
<!--(END)-->

<?ENDINC build/draft-ietf-httpbis-messaging-latest.iana-headers ?>
<t>
Furthermore, the field name "Close" is reserved, since using that name as
Expand DownExpand Up@@ -3100,20 +3099,20 @@ Upgrade: websocket
<x:ref>chunk-ext-val</x:ref> = token / quoted-string
<x:ref>chunk-size</x:ref> = 1*HEXDIG
<x:ref>chunked-body</x:ref> = *chunk last-chunk trailer-section CRLF
<x:ref>comment</x:ref> = &lt;comment, see <xref target="Semantics" x:fmt="," x:sec="4.4.1.3"/>&gt;
<x:ref>comment</x:ref> = &lt;comment, see <xref target="Semantics" x:fmt="," x:sec="5.4.1.3"/>&gt;
<x:ref>connection-option</x:ref> = token

<x:ref>field-line</x:ref> = field-name ":" OWS field-value OWS
<x:ref>field-name</x:ref> = &lt;field-name, see <xref target="Semantics" x:fmt="," x:sec="4.3"/>&gt;
<x:ref>field-value</x:ref> = &lt;field-value, see <xref target="Semantics" x:fmt="," x:sec="4.4"/>&gt;
<x:ref>field-name</x:ref> = &lt;field-name, see <xref target="Semantics" x:fmt="," x:sec="5.3"/>&gt;
<x:ref>field-value</x:ref> = &lt;field-value, see <xref target="Semantics" x:fmt="," x:sec="5.4"/>&gt;

<x:ref>last-chunk</x:ref> = 1*"0" [ chunk-ext ] CRLF

<x:ref>message-body</x:ref> = *OCTET
<x:ref>method</x:ref> = token

<x:ref>obs-fold</x:ref> = OWS CRLF RWS
<x:ref>obs-text</x:ref> = &lt;obs-text, see <xref target="Semantics" x:fmt="," x:sec="4.4.1.2"/>&gt;
<x:ref>obs-text</x:ref> = &lt;obs-text, see <xref target="Semantics" x:fmt="," x:sec="5.4.1.2"/>&gt;
<x:ref>origin-form</x:ref> = absolute-path [ "?" query ]

<x:ref>port</x:ref> = &lt;port, see <xref target="RFC3986" x:fmt="," x:sec="3.2.3"/>&gt;
Expand All@@ -3122,7 +3121,7 @@ Upgrade: websocket
<x:ref>protocol-version</x:ref> = token

<x:ref>query</x:ref> = &lt;query, see <xref target="RFC3986" x:fmt="," x:sec="3.4"/>&gt;
<x:ref>quoted-string</x:ref> = &lt;quoted-string, see <xref target="Semantics" x:fmt="," x:sec="4.4.1.2"/>&gt;
<x:ref>quoted-string</x:ref> = &lt;quoted-string, see <xref target="Semantics" x:fmt="," x:sec="5.4.1.2"/>&gt;

<x:ref>rank</x:ref> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
<x:ref>reason-phrase</x:ref> = 1*( HTAB / SP / VCHAR / obs-text )
Expand All@@ -3136,7 +3135,7 @@ Upgrade: websocket

<x:ref>t-codings</x:ref> = "trailers" / ( transfer-coding [ t-ranking ] )
<x:ref>t-ranking</x:ref> = OWS ";" OWS "q=" rank
<x:ref>token</x:ref> = &lt;token, see <xref target="Semantics" x:fmt="," x:sec="4.4.1.1"/>&gt;
<x:ref>token</x:ref> = &lt;token, see <xref target="Semantics" x:fmt="," x:sec="5.4.1.1"/>&gt;
<x:ref>trailer-section</x:ref> = *( field-line CRLF )
<x:ref>transfer-coding</x:ref> = token *( OWS ";" OWS transfer-parameter )
<x:ref>transfer-parameter</x:ref> = token BWS "=" BWS ( token / quoted-string )
Expand Down
79 changes: 75 additions & 4 deletionsdraft-ietf-httpbis-semantics-latest.xml
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -1067,6 +1067,56 @@ Content-Type: text/plain
<xref target="idempotent.methods"/>.
</t>
</section>
</section>

<section title="Extending and Versioning HTTP" anchor="extending.versioning">

<t>
While HTTP's core semantics don't change between protocol versions, the
expression of them "on the wire" can change, and so the
HTTP version number changes when incompatible changes are made to the wire
format. Additionally, HTTP allows incremental, backwards-compatible
changes to be made to the protocol without changing its version through
the use of defined extension points.
</t>

<section title="Extending HTTP" anchor="extending">
<t>
HTTP defines a number of generic extension points that can be used to
introduce capabilities to the protocol without introducing a new version,
including methods (<xref target="method.extensibility"/>), status codes
(<xref target="status.code.extensibility"/>), header and trailer fields
(<xref target="considerations.for.new.header.fields"/>), and further
extensibility points within defined fields (such as Cache-Control in <xref
target="cache.control.extensions"/>). Because the semantics of HTTP are
not versioned, these extension points are persistent; the version of the
protocol in use does not affect their semantics.
</t>
<t>
Version-independent extensions are discouraged from depending on or
interacting with the specific version of the protocol in use. When this is
unavoidable, careful consideration needs to be given to how the extension
can interoperate across versions.
</t>
<t>
Additionally, specific versions of HTTP might have their own extensibility
points, such as transfer-codings in HTTP/1.1 (<xref
target="field.transfer-encoding"/>) and HTTP/2 (<xref target="RFC7540"/>)
SETTINGS or frame types. These extension points are specific to the
version of the protocol they occur within.
</t>
<t>
Version-specific extensions cannot override or modify the semantics of
a version-independent mechanism or extension point (like a method or
header field) without explicitly being allowed by that protocol element. For
example, the CONNECT method (<xref target="CONNECT"/>) allows this.
</t>
<t>
These guidelines assure that the protocol operates correctly and
predictably, even when parts of the path implement different versions of
HTTP.
</t>
</section>

<section title="Protocol Versioning" anchor="protocol.version">
<t>
Expand DownExpand Up@@ -2146,7 +2196,6 @@ Content-Type: text/plain
</tbody>
</table>
<!--(END)-->

<?ENDINC build/draft-ietf-httpbis-semantics-latest.iana-headers ?>
</section>
</section>
Expand DownExpand Up@@ -4553,7 +4602,6 @@ Content-Range: exampleunit 11.2-14.3/25
</tbody>
</table>
<!--(END)-->

<?ENDINC build/draft-ietf-httpbis-semantics-latest.iana-methods ?>

<section title="Safe Methods" anchor="safe.methods">
Expand DownExpand Up@@ -5038,6 +5086,11 @@ Content-Range: exampleunit 11.2-14.3/25
through one or more proxies, which can then be secured using TLS
(Transport Layer Security, <xref target="RFC8446"/>).
</t>
<t>
Because CONNECT changes the request/response nature of an HTTP connection,
specific HTTP versions might have different ways of mapping its semantics
into the protocol's wire format.
</t>
Comment on lines +5089 to +5093
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I think you missed my second comment that this paragraph doesn't say anything useful. AIUI, CONNECT was recently extended to allow an origin server to process it, which wasn't about the wire format.

I would prefer that we update the first paragraph to be less specific to 1.1 and then reference the CONNECT extension as an example of an allowed semantic extension because the method had no applicability for an origin server before.

I am also fine with merging this now and fixing CONNECT later.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

RFC 7231 already permits origin servers to process CONNECT.

An origin server that receives a CONNECT request for itself MAY respond with a 2xx (Successful) status code to indicate that a connection is established. However, most origin servers do not implement CONNECT.

But yes, that extension stretches the bounds of this description.

<t>
CONNECT is intended only for use in requests to a proxy.
An origin server that receives a CONNECT request for itself &MAY;
Expand DownExpand Up@@ -7587,7 +7640,6 @@ Expect: 100-continue
</tbody>
</table>
<!--(END)-->

<?ENDINC build/draft-ietf-httpbis-semantics-latest.iana-status-codes ?>
<t>
Note that this list is not exhaustive &mdash; it does not include
Expand DownExpand Up@@ -10986,6 +11038,7 @@ Content-Encoding: gzip
<x:source href="draft-ietf-httpbis-cache-latest.xml" basename="draft-ietf-httpbis-cache-latest">
<x:has anchor="constructing.responses.from.caches"/>
<x:has anchor="cache-response-directive.private"/>
<x:has anchor="cache.control.extensions"/>
<x:has anchor="caching.authenticated.responses"/>
<x:has anchor="caching.negotiated.responses"/>
<x:has anchor="caching.overview"/>
Expand DownExpand Up@@ -11675,6 +11728,23 @@ Content-Encoding: gzip
<seriesInfo name='RFC' value='4918' />
</reference>

<reference anchor="RFC7540">
<front>
<title>Hypertext Transfer Protocol Version 2 (HTTP/2)</title>
<author initials="M." surname="Belshe" fullname="M. Belshe">
<organization/>
</author>
<author initials="R." surname="Peon" fullname="R. Peon">
<organization/>
</author>
<author initials="M." surname="Thomson" fullname="M. Thomson" role="editor">
<organization/>
</author>
<date year="2015" month="May"/>
</front>
<seriesInfo name="RFC" value="7540"/>
</reference>

<reference anchor="RFC8446">
<front>
<title>The Transport Layer Security (TLS) Protocol Version 1.3</title>
Expand DownExpand Up@@ -12605,7 +12675,8 @@ Content-Encoding: gzip
<li>In <xref target="field.accept"/> and <xref target="status.415"/>, allow "Accept" as response field (<eref target="https://github.com/httpwg/http-core/issues/48"/>)</li>
<li>In <xref target="field.name.registry"/>, add optional "Comments" entry (<eref target="https://github.com/httpwg/http-core/issues/273"/>)</li>
<li>In <xref target="field.values"/>, instruct recipients how to deal with control characters in field values (<eref target="https://github.com/httpwg/http-core/issues/377"/>)</li>
<li>In <xref target="field.values"/>, update note about field ABNF (<eref target="https://github.com/httpwg/http-core/issues/380"/>)</li>
<li>In <xref target="field.values"/>, update note about field ABNF (<eref target="https://github.com/httpwg/http-core/issues/380"/>)</li>
<li>Add <xref target="extending.versioning"/> about Extending and Versioning HTTP (<eref target="https://github.com/httpwg/http-core/issues/384"/>)</li>
<li>In <xref target="overview.of.status.codes"/>, include status 308 in list of heuristically cacheable status codes (<eref target="https://github.com/httpwg/http-core/issues/385"/>)</li>
</ul>
</section>
Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp