Changeset 1037


Ignore:
Timestamp:
Oct 19, 2010, 2:37:34 AM (9 years ago)
Author:
julian.reschke@…
Message:

Source reformat, update Changes section (see #230 and [1034])

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1036 r1037  
    543543         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#method">Method</a><ul class="toc">
    544544               <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#method.registry">Method Registry</a><ul class="toc">
    545                      <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.1.1">Considerations for New Methods</a></li>
     545                     <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.methods">Considerations for New Methods</a></li>
    546546                  </ul>
    547547               </li>
     
    792792      <p id="rfc.section.2.1.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-methods">http://www.iana.org/assignments/http-methods</a>&gt;.
    793793      </p>
    794       <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;Considerations for New Methods
    795       </h3>
     794      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="considerations.for.new.methods" href="#considerations.for.new.methods">Considerations for New Methods</a></h3>
    796795      <p id="rfc.section.2.1.1.p.1">When it is necessary to express new semantics for a HTTP request that aren't specific to a single application or media type,
    797796         and currently defined methods are inadequate, it may be appropriate to register a new method.
     
    26212620      <p id="rfc.section.C.13.p.1">Closed issues: </p>
    26222621      <ul>
     2622         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/230">http://tools.ietf.org/wg/httpbis/trac/ticket/230</a>&gt;: "Considerations for new methods"
     2623         </li>
    26232624         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/232">http://tools.ietf.org/wg/httpbis/trac/ticket/232</a>&gt;: "User-Agent guidelines" (relating to the 'User-Agent' header field)
    26242625         </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1036 r1037  
    482482</t>
    483483
    484 <section title="Considerations for New Methods">
    485 
    486   <t>When it is necessary to express new semantics for a HTTP request that
    487   aren't specific to a single application or media type, and currently defined
    488   methods are inadequate, it may be appropriate to register a new method.</t>
    489 
    490   <t>New methods &SHOULD; be potentially applicable to any resource. I.e.,
    491   they should not be specific to any particular media type, "type" of
    492   resource, or application.</t>
    493 
    494   <t>New methods &MUST-NOT; prohibit a message-body on either the request or
    495   the response message; however they &MAY; specify that only a zero-length
    496   body is allowed.</t>
    497 
    498   <t>New methods &MUST; define whether they are safe (<xref
    499   target="safe.methods"/>) and whether they are idempotent (<xref
    500   target="idempotent.methods"/>). They &MUST; also state whether they can be
    501   cached (&caching;); in particular what conditions a cache may store the
    502   response, and under what conditions such a stored response may be used to
    503   satisfy a subsequent request.</t>
    504 
    505   <t>New methods &SHOULD; explain how conditional request headers
    506   (&conditional;) affect the response (if there is any effect).</t>
    507 
    508   <t>HTTP methods &SHOULD; be registered in a document that isn't specific to
    509   a single application or other use of HTTP, so that it's clear that they are
    510   not specific to that application or extension.</t>
    511 
     484<section title="Considerations for New Methods" anchor="considerations.for.new.methods">
     485<t>
     486   When it is necessary to express new semantics for a HTTP request that
     487   aren't specific to a single application or media type, and currently defined
     488   methods are inadequate, it may be appropriate to register a new method.
     489</t>
     490<t>
     491   New methods &SHOULD; be potentially applicable to any resource. I.e.,
     492   they should not be specific to any particular media type, "type" of
     493   resource, or application.
     494</t>
     495<t>
     496   New methods &MUST-NOT; prohibit a message-body on either the request or
     497   the response message; however they &MAY; specify that only a zero-length
     498   body is allowed.
     499</t>
     500<t>
     501   New methods &MUST; define whether they are safe (<xref
     502   target="safe.methods"/>) and whether they are idempotent (<xref
     503   target="idempotent.methods"/>). They &MUST; also state whether they can be
     504   cached (&caching;); in particular what conditions a cache may store the
     505   response, and under what conditions such a stored response may be used to
     506   satisfy a subsequent request.
     507</t>
     508<t>
     509   New methods &SHOULD; explain how conditional request headers
     510   (&conditional;) affect the response (if there is any effect).
     511</t>
     512<t>
     513   HTTP methods &SHOULD; be registered in a document that isn't specific to
     514   a single application or other use of HTTP, so that it's clear that they are
     515   not specific to that application or extension.
     516</t>
    512517</section>
    513518
     
    38813886  <list style="symbols">
    38823887    <t>
     3888      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/230"/>:
     3889      "Considerations for new methods"
     3890    </t>
     3891    <t>
    38833892      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/232"/>:
    38843893      "User-Agent guidelines" (relating to the 'User-Agent' header field)
Note: See TracChangeset for help on using the changeset viewer.