Changeset 2586


Ignore:
Timestamp:
Jan 26, 2014, 12:14:42 AM (6 years ago)
Author:
fielding@…
Message:

(editorial) change encoding parameters MAY to can; see #531

Location:
draft-ietf-httpbis/latest
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r2585 r2586  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 29, 2014";
     450       content: "Expires July 30, 2014";
    451451  }
    452452  @bottom-right {
    … …  
    490490      <meta name="dct.creator" content="Reschke, J. F.">
    491491      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    492       <meta name="dct.issued" scheme="ISO8601" content="2014-01-25">
     492      <meta name="dct.issued" scheme="ISO8601" content="2014-01-26">
    493493      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    519519            <tr>
    520520               <td class="left">Intended status: Standards Track</td>
    521                <td class="right">January 25, 2014</td>
     521               <td class="right">January 26, 2014</td>
    522522            </tr>
    523523            <tr>
    524                <td class="left">Expires: July 29, 2014</td>
     524               <td class="left">Expires: July 30, 2014</td>
    525525               <td class="right"></td>
    526526            </tr>
    … …  
    551551            in progress”.
    552552         </p>
    553          <p>This Internet-Draft will expire on July 29, 2014.</p>
     553         <p>This Internet-Draft will expire on July 30, 2014.</p>
    554554      </div>
    555555      <div id="rfc.copyrightnotice">
    … …  
    14661466               <p id="rfc.section.3.3.1.p.6">Unlike <a href="p2-semantics.html#header.content-encoding" class="smpl">Content-Encoding</a> (<a href="p2-semantics.html#content.codings" title="Content Codings">Section 3.1.2.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>), Transfer-Encoding is a property of the message, not of the representation, and any recipient along the request/response
    14671467                  chain <em class="bcp14">MAY</em> decode the received transfer coding(s) or apply additional transfer coding(s) to the message body, assuming that corresponding
    1468                   changes are made to the Transfer-Encoding field-value. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
     1468                  changes are made to the Transfer-Encoding field-value. Additional information about the encoding parameters can be provided
     1469                  by other header fields not defined by this specification.
    14691470               </p>
    14701471               <p id="rfc.section.3.3.1.p.7">Transfer-Encoding <em class="bcp14">MAY</em> be sent in a response to a HEAD request or in a <a href="p4-conditional.html#status.304" class="smpl">304 (Not Modified)</a> response (<a href="p4-conditional.html#status.304" title="304 Not Modified">Section 4.1</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>) to a GET request, neither of which includes a message body, to indicate that the origin server would have applied a transfer

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2585 r2586  
    15941594   transfer coding(s) or apply additional transfer coding(s) to the message
    15951595   body, assuming that corresponding changes are made to the Transfer-Encoding
    1596    field-value. Additional information about the encoding parameters &MAY; be
     1596   field-value. Additional information about the encoding parameters can be
    15971597   provided by other header fields not defined by this specification.
    15981598</t>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r2580 r2586  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 28, 2014";
     450       content: "Expires July 30, 2014";
    451451  }
    452452  @bottom-right {
    … …  
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2014-01-24">
     495      <meta name="dct.issued" scheme="ISO8601" content="2014-01-26">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
    … …  
    521521            <tr>
    522522               <td class="left">Intended status: Standards Track</td>
    523                <td class="right">January 24, 2014</td>
     523               <td class="right">January 26, 2014</td>
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: July 28, 2014</td>
     526               <td class="left">Expires: July 30, 2014</td>
    527527               <td class="right"></td>
    528528            </tr>
    … …  
    553553            in progress”.
    554554         </p>
    555          <p>This Internet-Draft will expire on July 28, 2014.</p>
     555         <p>This Internet-Draft will expire on July 30, 2014.</p>
    556556      </div>
    557557      <div id="rfc.copyrightnotice">
    … …  
    10331033                  <div id="rfc.figure.u.9"></div><pre class="text">  Content-Encoding: gzip
    10341034</pre><p id="rfc.section.3.1.2.2.p.5">If one or more encodings have been applied to a representation, the sender that applied the encodings <em class="bcp14">MUST</em> generate a Content-Encoding header field that lists the content codings in the order in which they were applied. Additional
    1035                      information about the encoding parameters <em class="bcp14">MAY</em> be provided by other header fields not defined by this specification.
     1035                     information about the encoding parameters can be provided by other header fields not defined by this specification.
    10361036                  </p>
    10371037                  <p id="rfc.section.3.1.2.2.p.6">Unlike Transfer-Encoding (<a href="p1-messaging.html#header.transfer-encoding" title="Transfer-Encoding">Section 3.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), the codings listed in Content-Encoding are a characteristic of the representation; the representation is defined in terms

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2580 r2586  
    591591   that applied the encodings &MUST; generate a Content-Encoding header field
    592592   that lists the content codings in the order in which they were applied.
    593    Additional information about the encoding parameters &MAY; be provided
     593   Additional information about the encoding parameters can be provided
    594594   by other header fields not defined by this specification.
    595595</t>
Note: See TracChangeset for help on using the changeset viewer.