Ignore:
Timestamp:
26/01/14 08:14:42 (8 years ago)
Author:
fielding@…
Message:

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

File:
1 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
Note: See TracChangeset for help on using the changeset viewer.