Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adjust section titles #525

Merged
merged 1 commit into from
Nov 25, 2020
Merged
Changes from all 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
52 changes: 26 additions & 26 deletions draft-ietf-httpbis-semantics-latest.xml
Original file line number Diff line number Diff line change
@@ -169,7 +169,7 @@
</t>
</section>

<section title="Evolution" anchor="intro.evolution">
<section title="History and Evolution" anchor="intro.evolution">
<t>
HTTP has been the primary information transfer protocol for the World Wide
Web since its introduction in 1990. It began as a trivial mechanism for
@@ -226,7 +226,7 @@
</t>
</section>

<section title="Semantics" anchor="intro.semantics">
<section title="Core Semantics" anchor="intro.semantics">
<t>
HTTP provides a uniform interface for interacting with a resource
(<xref target="resources"/>), regardless of its type, nature, or
@@ -260,7 +260,7 @@
</t>
</section>

<section title="Obsoletes" anchor="intro.obsoletes">
<section title="Specifications Obsoleted by this Document" anchor="intro.obsoletes">
<t>
This document obsoletes the following specifications:
</t>
@@ -502,7 +502,7 @@
</section>
</section>

<section title="Terminology" anchor="terminology">
<section title="Terminology and Core Concepts" anchor="terminology">
<t>
HTTP was created for the World Wide Web (WWW) architecture
and has evolved over time to support the scalability needs of a worldwide
@@ -851,7 +851,7 @@ Content-Type: text/plain
</section>
</section>

<section title="Identifiers" anchor="uri">
<section title="Identifiers in HTTP" anchor="uri">
<iref primary="true" item="URI"/>
<iref primary="false" item="resource"/>
<t>
@@ -919,7 +919,7 @@ Content-Type: text/plain
</t>
</section>

<section title="URI Schemes" anchor="uri.schemes">
<section title="HTTP-Related URI Schemes" anchor="uri.schemes">
<t>
IANA maintains the registry of URI Schemes <xref target="BCP35"/> at
<eref target="https://www.iana.org/assignments/uri-schemes/"/>.
@@ -1071,7 +1071,7 @@ Content-Type: text/plain
</artwork>
</section>

<section title="http(s) Deprecated userinfo" anchor="http.userinfo">
<section title="Deprecation of userinfo in http(s) URIs" anchor="http.userinfo">
<t>
The URI generic syntax for authority also includes a userinfo subcomponent
(<xref target="RFC3986" x:fmt="," x:sec="3.2.1"/>) for including user
@@ -1414,7 +1414,7 @@ Content-Type: text/plain
</t>
</section>

<section title="Framing" anchor="message.framing">
<section title="Message Framing" anchor="message.framing">
<iref primary="true" item="complete"/>
<iref primary="true" item="incomplete"/>
<t>
@@ -1730,7 +1730,7 @@ Content-Type: text/plain
</section>
</section>

<section title="Payload" anchor="payload">
<section title="Message Payload" anchor="payload">
<iref item="payload"/>
<t>
Some HTTP messages transfer a complete or partial representation as the
@@ -1765,7 +1765,7 @@ Content-Type: text/plain
</t>
</section>

<section title="Identification" anchor="identifying.payload">
<section title="Identifying Message Payloads" anchor="identifying.payload">
<t>
When a complete or partial representation is transferred in a message
payload, it is often desirable for the sender to supply, or the recipient
@@ -1928,7 +1928,7 @@ Content-Type: text/plain
</t>
</section>

<section title="Processing" anchor="trailers.processing">
<section title="Processing Trailer Fields" anchor="trailers.processing">
<t>
Like header fields, trailer fields with the same name are processed in the
order received; multiple trailer field lines with the same name have the
@@ -2352,7 +2352,7 @@ Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format
</section>
</section>

<section title="Routing" anchor="routing">
<section title="Routing HTTP Messages" anchor="routing">
<t>
HTTP is used in a wide variety of applications, ranging from
general-purpose computers to home appliances. In some cases,
@@ -2367,7 +2367,7 @@ Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format
response routing follows the same connection chain back to the client.
</t>

<section title="Target Resource" anchor="target.resource">
<section title="Target Resources" anchor="target.resource">
<iref primary="true" item="target resource"/>
<iref primary="true" item="target URI"/>
<x:anchor-alias value="target resource"/>
@@ -2481,7 +2481,7 @@ Host: www.example.org
</section>
</section>

<section title="Routing Inbound" anchor="routing.inbound">
<section title="Routing Inbound Requests" anchor="routing.inbound">
<t>
Once the target URI and its origin are determined, a client decides whether
a network request is necessary to accomplish the desired semantics and,
@@ -2786,7 +2786,7 @@ Host: www.example.org
</section>
</section>

<section title="Transformations" anchor="message.transformations">
<section title="Message Transformations" anchor="message.transformations">
<iref primary="true" item="transforming proxy"/>
<iref primary="true" item="non-transforming proxy"/>
<t>
@@ -3004,7 +3004,7 @@ Upgrade: websocket
that help guide the recipient's future interactions.
</t>

<section title="Selected Representation" anchor="selected.representation">
<section title="Selected Representations" anchor="selected.representation">
<iref primary="true" item="selected representation"/>
<x:anchor-alias value="selected representation"/>
<t>
@@ -3021,7 +3021,7 @@ Upgrade: websocket
</t>
</section>

<section title="Data" anchor="representation.data">
<section title="Representation Data" anchor="representation.data">
<x:anchor-alias value="representation-data"/>
<t>
The representation data associated with an HTTP message is
@@ -3040,7 +3040,7 @@ Upgrade: websocket
</artwork>
</section>

<section title="Metadata" anchor="representation.metadata">
<section title="Representation Metadata" anchor="representation.metadata">
<x:anchor-alias value="representation-header"/>
<t>
Representation header fields provide metadata about the representation.
@@ -3718,7 +3718,7 @@ Upgrade: websocket
</t>
</section>

<section title="Validators" anchor="response.validator">
<section title="Validator Fields" anchor="response.validator">
<iref primary="true" item="metadata"/>
<iref primary="true" item="validator"/>
<iref item="selected representation"/>
@@ -5045,7 +5045,7 @@ Proxy-Authorization: basic aGVsbG86d29ybGQ=
</section>
</section>

<section title="Context" anchor="context">
<section title="Message Context" anchor="context">

<section title="Request Context" anchor="request.context">
<x:anchor-alias value="request-header"/>
@@ -5779,7 +5779,7 @@ Expect: 100-continue
</section>
</section>

<section title="Authentication" anchor="authentication">
<section title="HTTP Authentication" anchor="authentication">
<section title="Authentication Scheme" anchor="auth.scheme">
<x:anchor-alias value="auth-scheme"/>
<t>
@@ -5937,7 +5937,7 @@ Expect: 100-continue
</t>
</section>

<section title="Protection Space (Realm)" anchor="protection.space">
<section title="Establishing a Protection Space (Realm)" anchor="protection.space">
<iref item="Protection Space"/>
<iref item="Realm"/>
<iref item="Canonical Root URI"/>
@@ -5976,7 +5976,7 @@ Expect: 100-continue
</t>
</section>

<section title="Authenticating User to Origin Server" anchor="auth.user.origin.server">
<section title="Authenticating Users to Origin Servers" anchor="auth.user.origin.server">

<section title="WWW-Authenticate" anchor="field.www-authenticate">
<x:anchor-alias value="header.www-authenticate"/>
@@ -6104,7 +6104,7 @@ Expect: 100-continue
</section>
</section>

<section title="Authenticating Client to Proxy" anchor="auth.client.proxy">
<section title="Authenticating Clients to Proxies" anchor="auth.client.proxy">

<section title="Proxy-Authenticate" anchor="field.proxy-authenticate">
<x:anchor-alias value="header.proxy-authenticate"/>
@@ -7402,7 +7402,7 @@ Expect: 100-continue
</section>
</section>

<section title="Evaluation" anchor="evaluation">
<section title="Evaluation of Preconditions" anchor="evaluation">
<t>
Except when excluded below, a recipient cache or origin server &MUST;
evaluate received request preconditions after it has successfully performed
@@ -7452,7 +7452,7 @@ Expect: 100-continue
</t>
</section>

<section title="Precedence" anchor="precedence">
<section title="Precedence of Preconditions" anchor="precedence">
<t>
When more than one conditional request header field is present in a request,
the order in which the fields are evaluated becomes important. In practice,