Ignore:
Timestamp:
Jul 28, 2009, 8:02:09 AM (10 years ago)
Author:
fielding@…
Message:

first pass at cleaning up message parsing definition: header fields.

File:
1 edited

Legend:

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

    r632 r647  
    471471         <tr>
    472472            <td class="header left"></td>
    473             <td class="header right">July 27, 2009</td>
     473            <td class="header right">July 28, 2009</td>
    474474         </tr>
    475475      </table>
     
    15441544         </p>
    15451545      </div>
    1546       <p id="rfc.section.9.4.p.6">There are circumstances in which a fragment identifier in a Location URL would not be appropriate: </p>
     1546      <p id="rfc.section.9.4.p.6">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p>
    15471547      <ul>
    1548          <li>With a 201 Created response, because in this usage the Location header specifies the URL for the entire created resource.</li>
     1548         <li>With a 201 Created response, because in this usage the Location header specifies the URI for the entire created resource.</li>
    15491549         <li>With a 300 Multiple Choices, since the choice decision is intended to be made on resource characteristics and not fragment
    15501550            characteristics.
Note: See TracChangeset for help on using the changeset viewer.