Changeset 746 for draft-ietf-httpbis


Ignore:
Timestamp:
Jan 17, 2010, 6:33:08 AM (10 years ago)
Author:
julian.reschke@…
Message:

Editorial: use consistent quoting style (double quotes, in particular no back quotes)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r744 r746  
    404404      <meta name="DC.Creator" content="Reschke, J. F.">
    405405      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    406       <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-08">
     406      <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17">
    407407      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    408408      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: July 12, 2010</td>
     437               <td class="left">Expires: July 21, 2010</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">January 8, 2010</td>
     490               <td class="right">January 17, 2010</td>
    491491            </tr>
    492492         </tbody>
     
    520520      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    521521      </p>
    522       <p>This Internet-Draft will expire in July 12, 2010.</p>
     522      <p>This Internet-Draft will expire in July 21, 2010.</p>
    523523      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    524524      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    16401640      <p id="rfc.section.6.4.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;9.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
    16411641         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
    1642          a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
     1642         a quality value of 0, then content with this parameter is "not acceptable" for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
    16431643      </p>
    16441644      <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.92"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )
     
    18771877      </p>
    18781878      <div id="rfc.figure.u.57"></div><pre class="text">  Connection: close
    1879 </pre><p id="rfc.section.9.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered `persistent' (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;7.1</a>) after the current request/response is complete.
     1879</pre><p id="rfc.section.9.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered "persistent" (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;7.1</a>) after the current request/response is complete.
    18801880      </p>
    18811881      <p id="rfc.section.9.1.p.9">An HTTP/1.1 client that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every request message.
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r744 r746  
    20882088   the range 0 through 1, where 0 is the minimum and 1 the maximum
    20892089   value. If a parameter has a quality value of 0, then content with
    2090    this parameter is `not acceptable' for the client. HTTP/1.1
     2090   this parameter is "not acceptable" for the client. HTTP/1.1
    20912091   applications &MUST-NOT; generate more than three digits after the
    20922092   decimal point. User configuration of these values &SHOULD; also be
     
    26062606<t>
    26072607   in either the request or the response header fields indicates that
    2608    the connection &SHOULD-NOT;  be considered `persistent' (<xref target="persistent.connections"/>)
     2608   the connection &SHOULD-NOT;  be considered "persistent" (<xref target="persistent.connections"/>)
    26092609   after the current request/response is complete.
    26102610</t>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r741 r746  
    403403      <meta name="DC.Creator" content="Reschke, J. F.">
    404404      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    405       <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-01">
     405      <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17">
    406406      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    407407      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields.">
     
    434434            </tr>
    435435            <tr>
    436                <td class="left">Expires: July 5, 2010</td>
     436               <td class="left">Expires: July 21, 2010</td>
    437437               <td class="right">HP</td>
    438438            </tr>
     
    487487            <tr>
    488488               <td class="left"></td>
    489                <td class="right">January 1, 2010</td>
     489               <td class="right">January 17, 2010</td>
    490490            </tr>
    491491         </tbody>
     
    518518      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    519519      </p>
    520       <p>This Internet-Draft will expire in July 5, 2010.</p>
     520      <p>This Internet-Draft will expire in July 21, 2010.</p>
    521521      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    522522      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    927927         <li>Otherwise, the response is a representation of an anonymous (i.e., unidentified) resource.</li>
    928928      </ol>
    929       <p id="rfc.section.6.1.p.5"> <span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: Note that 'request-URI' is used here; however, we need to come up with a term to denote "the URI that can be inferred from
     929      <p id="rfc.section.6.1.p.5"> <span class="comment" id="TODO-req-uri">[<a href="#TODO-req-uri" class="smpl">TODO-req-uri</a>: Note that "request-URI" is used here; however, we need to come up with a term to denote "the URI that can be inferred from
    930930            examining the request-target and the Host header." (see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;). Also, the comparison function is going to have to be defined somewhere, because we already need to compare URIs for things
    931931            like cache invalidation.]</span>
     
    10501050         the resource with that URI. If a new resource is created at the request-target, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
    10511051         Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the request-target,
    1052          an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix 'Content-') that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
     1052         an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* headers (headers starting with the prefix "Content-") that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
    10531053      </p>
    10541054      <p id="rfc.section.7.6.p.2">If the request passes through a cache and the request-target identifies one or more currently cached entities, those entries <em class="bcp14">SHOULD</em> be treated as stale. Responses to this method are not cacheable.
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r741 r746  
    691691<t>
    692692  <cref anchor="TODO-req-uri">
    693    Note that 'request-URI' is used here; however, we need to come up with a
     693   Note that "request-URI" is used here; however, we need to come up with a
    694694   term to denote "the URI that can be inferred from examining the
    695695   request-target and the Host header." (see <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/196" />).
     
    956956   error response &SHOULD; be given that reflects the nature of the
    957957   problem. The recipient of the entity &MUST-NOT; ignore any Content-*
    958    headers (headers starting with the prefix 'Content-') that it does
     958   headers (headers starting with the prefix "Content-") that it does
    959959   not understand or implement
    960960   and &MUST; return a 501 (Not Implemented) response in such cases.
  • draft-ietf-httpbis/latest/p3-payload.html

    r745 r746  
    401401      <meta name="DC.Creator" content="Reschke, J. F.">
    402402      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    403       <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-15">
     403      <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17">
    404404      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    405405      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
     
    427427            </tr>
    428428            <tr>
    429                <td class="left">Expires: July 19, 2010</td>
     429               <td class="left">Expires: July 21, 2010</td>
    430430               <td class="right">J. Mogul</td>
    431431            </tr>
     
    484484            <tr>
    485485               <td class="left"></td>
    486                <td class="right">January 15, 2010</td>
     486               <td class="right">January 17, 2010</td>
    487487            </tr>
    488488         </tbody>
     
    514514      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    515515      </p>
    516       <p>This Internet-Draft will expire in July 19, 2010.</p>
     516      <p>This Internet-Draft will expire in July 21, 2010.</p>
    517517      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    518518      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    674674      <ul class="empty">
    675675         <li>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
    676             is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
     676            is termed a "variant". Use of the term "variant" does not necessarily imply that the resource is subject to content negotiation.
    677677         </li>
    678678      </ul>
     
    17771777      </p>
    17781778      <p id="rfc.section.B.1.p.6">If this header is used in a response with the application/octet-stream content-type, the implied suggestion is that the user
    1779          agent should not display the response, but directly enter a `save response as...' dialog.
     1779         agent should not display the response, but directly enter a "save response as..." dialog.
    17801780      </p>
    17811781      <p id="rfc.section.B.1.p.7">See <a href="#content-disposition.issues" title="Content-Disposition Issues">Section&nbsp;7.2</a> for Content-Disposition security issues.
  • draft-ietf-httpbis/latest/p3-payload.xml

    r745 r746  
    286286      A resource may have one, or more than one, representation(s)
    287287      associated with it at any given instant. Each of these
    288       representations is termed a `variant'.  Use of the term `variant'
     288      representations is termed a "variant".  Use of the term "variant"
    289289      does not necessarily imply that the resource is subject to content
    290290      negotiation.
     
    26702670   If this header is used in a response with the application/octet-stream
    26712671   content-type, the implied suggestion is that the user agent
    2672    should not display the response, but directly enter a `save response
    2673    as...' dialog.
     2672   should not display the response, but directly enter a "save response
     2673   as..." dialog.
    26742674</t>
    26752675<t>
  • draft-ietf-httpbis/latest/p4-conditional.html

    r741 r746  
    400400      <meta name="DC.Creator" content="Reschke, J. F.">
    401401      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    402       <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-01">
     402      <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-15">
    403403      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    404404      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
     
    426426            </tr>
    427427            <tr>
    428                <td class="left">Expires: July 5, 2010</td>
     428               <td class="left">Expires: July 19, 2010</td>
    429429               <td class="right">J. Mogul</td>
    430430            </tr>
     
    483483            <tr>
    484484               <td class="left"></td>
    485                <td class="right">January 1, 2010</td>
     485               <td class="right">January 15, 2010</td>
    486486            </tr>
    487487         </tbody>
     
    513513      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    514514      </p>
    515       <p>This Internet-Draft will expire in July 5, 2010.</p>
     515      <p>This Internet-Draft will expire in July 19, 2010.</p>
    516516      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    517517      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p5-range.html

    r741 r746  
    400400      <meta name="DC.Creator" content="Reschke, J. F.">
    401401      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    402       <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-01">
     402      <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17">
    403403      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    404404      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">
     
    426426            </tr>
    427427            <tr>
    428                <td class="left">Expires: July 5, 2010</td>
     428               <td class="left">Expires: July 21, 2010</td>
    429429               <td class="right">J. Mogul</td>
    430430            </tr>
     
    483483            <tr>
    484484               <td class="left"></td>
    485                <td class="right">January 1, 2010</td>
     485               <td class="right">January 17, 2010</td>
    486486            </tr>
    487487         </tbody>
     
    513513      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    514514      </p>
    515       <p>This Internet-Draft will expire in July 5, 2010.</p>
     515      <p>This Internet-Draft will expire in July 21, 2010.</p>
    516516      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    517517      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    800800         to obtain the entire current entity-body.
    801801      </p>
    802       <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is `if
    803          the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity'.
     802      <p id="rfc.section.5.3.p.2">The "If-Range" request-header field allows a client to "short-circuit" the second request. Informally, its meaning is "if
     803         the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity".
    804804      </p>
    805805      <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.if-range" class="smpl">If-Range</a>   = "If-Range" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-range" class="smpl">If-Range-v</a>
  • draft-ietf-httpbis/latest/p5-range.xml

    r741 r746  
    656656<t>
    657657   The "If-Range" request-header field allows a client to "short-circuit" the second
    658    request. Informally, its meaning is `if the entity is unchanged, send
     658   request. Informally, its meaning is "if the entity is unchanged, send
    659659   me the part(s) that I am missing; otherwise, send me the entire new
    660    entity'.
     660   entity".
    661661</t>
    662662<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Range"/><iref primary="true" item="Grammar" subitem="If-Range-v"/>
  • draft-ietf-httpbis/latest/p7-auth.html

    r741 r746  
    394394      <meta name="DC.Creator" content="Reschke, J. F.">
    395395      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    396       <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-01">
     396      <meta name="DC.Date.Issued" scheme="ISO8601" content="2010-01-17">
    397397      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    398398      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
     
    425425            </tr>
    426426            <tr>
    427                <td class="left">Expires: July 5, 2010</td>
     427               <td class="left">Expires: July 21, 2010</td>
    428428               <td class="right">HP</td>
    429429            </tr>
     
    478478            <tr>
    479479               <td class="left"></td>
    480                <td class="right">January 1, 2010</td>
     480               <td class="right">January 17, 2010</td>
    481481            </tr>
    482482         </tbody>
     
    508508      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    509509      </p>
    510       <p>This Internet-Draft will expire in July 5, 2010.</p>
     510      <p>This Internet-Draft will expire in July 21, 2010.</p>
    511511      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    512512      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    787787            the user for credentials.
    788788         </li>
    789          <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
    790             the server side of the application `knows' that there is no further reason for the client to retain the credentials.
     789         <li>Applications which include a session termination indication (such as a "logout" or "commit" button on a page) after which
     790            the server side of the application "knows" that there is no further reason for the client to retain the credentials.
    791791         </li>
    792792      </ul>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r741 r746  
    576576
    577577     <t>Applications which include a session termination indication
    578         (such as a `logout' or `commit' button on a page) after which
    579         the server side of the application `knows' that there is no
     578        (such as a "logout" or "commit" button on a page) after which
     579        the server side of the application "knows" that there is no
    580580        further reason for the client to retain the credentials.</t>
    581581  </list>
Note: See TracChangeset for help on using the changeset viewer.