Ignore:
Timestamp:
Nov 14, 2008, 4:44:55 PM (11 years ago)
Author:
julian.reschke@…
Message:

Merge in Roy's changes wrt Introduction and HTTP Architecture, replace Request-URI by request-target and relative-URI by partial-URI throughout.

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r386 r391  
    333333  <x:anchor-alias value="If-Range"/>
    334334  <x:anchor-alias value="If-Unmodified-Since"/>
     335  <x:anchor-alias value="partial-URI"/>
    335336  <x:anchor-alias value="product"/>
    336337  <x:anchor-alias value="Proxy-Authenticate"/>
    337338  <x:anchor-alias value="Proxy-Authorization"/>
    338339  <x:anchor-alias value="Range"/>
    339   <x:anchor-alias value="relativeURI"/>
    340340  <x:anchor-alias value="TE"/>
    341341  <x:anchor-alias value="Vary"/>
    … …  
    348348  <x:ref>Host</x:ref>          = &lt;Host, defined in &uri;&gt;
    349349  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &full-date;&gt;
     350  <x:ref>partial-URI</x:ref>   = &lt;partial-URI, defined in &uri;&gt;
    350351  <x:ref>product</x:ref>       = &lt;product, defined in &product-tokens;&gt;
    351   <x:ref>relativeURI</x:ref>   = &lt;relativeURI, defined in &uri;&gt;
    352352  <x:ref>TE</x:ref>            = &lt;TE, defined in &header-te;&gt;
    353353</artwork></figure>
    … …  
    395395<t>
    396396   The Method  token indicates the method to be performed on the
    397    resource identified by the Request-URI. The method is case-sensitive.
     397   resource identified by the request-target. The method is case-sensitive.
    398398</t>
    399399<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Method"/><iref primary="true" item="Grammar" subitem="extension-method"/>
    … …  
    541541       / "412"  ; <xref target="status.412"/>: Precondition Failed
    542542       / "413"  ; <xref target="status.413"/>: Request Entity Too Large
    543        / "414"  ; <xref target="status.414"/>: Request-URI Too Large
     543       / "414"  ; <xref target="status.414"/>: Request-target Too Large
    544544       / "415"  ; <xref target="status.415"/>: Unsupported Media Type
    545545       / "416"  ; <xref target="status.416"/>: Requested range not satisfiable
    … …  
    596596   information about the response which cannot be placed in the Status-Line.
    597597   These header fields give information about the server and about
    598    further access to the resource identified by the Request-URI.
     598   further access to the resource identified by the request-target.
    599599</t>
    600600<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="response-header"/>
    … …  
    706706   The OPTIONS method represents a request for information about the
    707707   communication options available on the request/response chain
    708    identified by the Request-URI. This method allows the client to
     708   identified by the request-target. This method allows the client to
    709709   determine the options and/or requirements associated with a resource,
    710710   or the capabilities of a server, without implying a resource action
    … …  
    723723</t>
    724724<t>
    725    If the Request-URI is an asterisk ("*"), the OPTIONS request is
     725   If the request-target is an asterisk ("*"), the OPTIONS request is
    726726   intended to apply to the server in general rather than to a specific
    727727   resource. Since a server's communication options typically depend on
    … …  
    732732</t>
    733733<t>
    734    If the Request-URI is not an asterisk, the OPTIONS request applies
     734   If the request-target is not an asterisk, the OPTIONS request applies
    735735   only to the options that are available when communicating with that
    736736   resource.
    … …  
    770770<t>
    771771   The GET method means retrieve whatever information (in the form of an
    772    entity) is identified by the Request-URI. If the Request-URI refers
     772   entity) is identified by the request-target. If the request-target refers
    773773   to a data-producing process, it is the produced data which shall be
    774774   returned as the entity in the response and not the source text of the
    … …  
    835835   The POST method is used to request that the origin server accept the
    836836   entity enclosed in the request as data to be processed by the resource
    837    identified by the Request-URI in the Request-Line. POST is designed
     837   identified by the request-target in the Request-Line. POST is designed
    838838   to allow a uniform method to cover the following functions:
    839839  <list style="symbols">
    … …  
    856856<t>
    857857   The actual function performed by the POST method is determined by the
    858    server and is usually dependent on the Request-URI.
     858   server and is usually dependent on the request-target.
    859859</t>
    860860<t>
    … …  
    884884<t>
    885885   The PUT method requests that the enclosed entity be stored at the
    886    supplied Request-URI. If the Request-URI refers to an already
     886   supplied request-target. If the request-target refers to an already
    887887   existing resource, the enclosed entity &SHOULD; be considered as a
    888888   modified version of the one residing on the origin server. If the
    889    Request-URI does not point to an existing resource, and that URI is
     889   request-target does not point to an existing resource, and that URI is
    890890   capable of being defined as a new resource by the requesting user
    891891   agent, the origin server can create the resource with that URI. If a
    892    new resource is created at the Request-URI, the origin server &MUST;
     892   new resource is created at the request-target, the origin server &MUST;
    893893         inform the user agent
    894894   via the 201 (Created) response. If an existing resource is modified,
    895895   either the 200 (OK) or 204 (No Content) response codes &SHOULD; be sent
    896896   to indicate successful completion of the request. If the resource
    897    could not be created or modified with the Request-URI, an appropriate
     897   could not be created or modified with the request-target, an appropriate
    898898   error response &SHOULD; be given that reflects the nature of the
    899899   problem. The recipient of the entity &MUST-NOT; ignore any Content-*
    … …  
    903903</t>
    904904<t>
    905    If the request passes through a cache and the Request-URI identifies
     905   If the request passes through a cache and the request-target identifies
    906906   one or more currently cached entities, those entries &SHOULD; be
    907907   treated as stale. Responses to this method are not cacheable.
    … …  
    909909<t>
    910910   The fundamental difference between the POST and PUT requests is
    911    reflected in the different meaning of the Request-URI. The URI in a
     911   reflected in the different meaning of the request-target. The URI in a
    912912   POST request identifies the resource that will handle the enclosed
    913913   entity. That resource might be a data-accepting process, a gateway to
    … …  
    944944<t>
    945945   The DELETE method requests that the origin server delete the resource
    946    identified by the Request-URI. This method &MAY; be overridden by human
     946   identified by the request-target. This method &MAY; be overridden by human
    947947   intervention (or other means) on the origin server. The client cannot
    948948   be guaranteed that the operation has been carried out, even if the
    … …  
    960960</t>
    961961<t>
    962    If the request passes through a cache and the Request-URI identifies
     962   If the request passes through a cache and the request-target identifies
    963963   one or more currently cached entities, those entries &SHOULD; be
    964964   treated as stale. Responses to this method are not cacheable.
    … …  
    12671267   future references to this resource &SHOULD; use one of the returned
    12681268   URIs.  Clients with link editing capabilities ought to automatically
    1269    re-link references to the Request-URI to one or more of the new
     1269   re-link references to the request-target to one or more of the new
    12701270   references returned by the server, where possible. This response is
    12711271   cacheable unless indicated otherwise.
    … …  
    12981298   The requested resource resides temporarily under a different URI.
    12991299   Since the redirection might be altered on occasion, the client &SHOULD;
    1300    continue to use the Request-URI for future requests.  This response
     1300   continue to use the request-target for future requests.  This response
    13011301   is only cacheable if indicated by a Cache-Control or Expires header
    13021302   field.
    … …  
    14001400   The requested resource resides temporarily under a different URI.
    14011401   Since the redirection &MAY; be altered on occasion, the client &SHOULD;
    1402    continue to use the Request-URI for future requests.  This response
     1402   continue to use the request-target for future requests.  This response
    14031403   is only cacheable if indicated by a Cache-Control or Expires header
    14041404   field.
    … …  
    14871487  <iref primary="true" item="Status Codes" subitem="404 Not Found" x:for-anchor=""/>
    14881488<t>
    1489    The server has not found anything matching the Request-URI. No
     1489   The server has not found anything matching the request-target. No
    14901490   indication is given of whether the condition is temporary or
    14911491   permanent. The 410 (Gone) status code &SHOULD; be used if the server
    … …  
    15031503<t>
    15041504   The method specified in the Request-Line is not allowed for the
    1505    resource identified by the Request-URI. The response &MUST; include an
     1505   resource identified by the request-target. The response &MUST; include an
    15061506   Allow header containing a list of valid methods for the requested
    15071507   resource.
    … …  
    15921592   forwarding address is known. This condition is expected to be
    15931593   considered permanent. Clients with link editing capabilities &SHOULD;
    1594    delete references to the Request-URI after user approval. If the
     1594   delete references to the request-target after user approval. If the
    15951595   server does not know, or has no facility to determine, whether or not
    15961596   the condition is permanent, the status code 404 (Not Found) &SHOULD; be
    … …  
    16471647</section>
    16481648
    1649 <section title="414 Request-URI Too Long" anchor="status.414">
    1650   <iref primary="true" item="414 Request-URI Too Long (status code)" x:for-anchor=""/>
    1651   <iref primary="true" item="Status Codes" subitem="414 Request-URI Too Long" x:for-anchor=""/>
    1652 <t>
    1653    The server is refusing to service the request because the Request-URI
     1649<section title="414 Request-target Too Long" anchor="status.414">
     1650  <iref primary="true" item="414 Request-target Too Long (status code)" x:for-anchor=""/>
     1651  <iref primary="true" item="Status Codes" subitem="414 Request-target Too Long" x:for-anchor=""/>
     1652<t>
     1653   The server is refusing to service the request because the request-target
    16541654   is longer than the server is willing to interpret. This rare
    16551655   condition is only likely to occur when a client has improperly
    … …  
    16591659   itself), or when the server is under attack by a client attempting to
    16601660   exploit security holes present in some servers using fixed-length
    1661    buffers for reading or manipulating the Request-URI.
     1661   buffers for reading or manipulating the request-target.
    16621662</t>
    16631663</section>
    … …  
    18041804<t>
    18051805      The response-header field "Allow" lists the set of methods advertised as
    1806       supported by the resource identified by the Request-URI. The purpose of
     1806      supported by the resource identified by the request-target. The purpose of
    18071807      this field is strictly to inform the recipient of valid methods
    18081808      associated with the resource. An Allow header field &MUST; be
    … …  
    19431943   The response-header field "Location" is used for the identification of a
    19441944   new resource or to redirect the recipient to a location other than the
    1945    Request-URI for completion of the request.  For 201 (Created)
     1945   request-target for completion of the request.  For 201 (Created)
    19461946   responses, the Location is that of the new resource which was created
    19471947   by the request. For 3xx responses, the location &SHOULD; indicate the
    … …  
    20232023   The request-header field "Referer" [sic] allows the client to specify,
    20242024   for the server's benefit, the address (URI) of the resource from
    2025    which the Request-URI was obtained (the "referrer", although the
     2025   which the request-target was obtained (the "referrer", although the
    20262026   header field is misspelled.) The Referer request-header allows a
    20272027   server to generate lists of back-links to resources for interest,
    20282028   logging, optimized caching, etc. It also allows obsolete or mistyped
    20292029   links to be traced for maintenance. The Referer field &MUST-NOT; be
    2030    sent if the Request-URI was obtained from a source that does not have
     2030   sent if the request-target was obtained from a source that does not have
    20312031   its own URI, such as input from the user keyboard.
    20322032</t>
    20332033<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Referer"/><iref primary="true" item="Grammar" subitem="Referer-v"/>
    20342034  <x:ref>Referer</x:ref>        = "Referer" ":" <x:ref>OWS</x:ref> <x:ref>Referer-v</x:ref>
    2035   <x:ref>Referer-v</x:ref>      = <x:ref>absolute-URI</x:ref> / <x:ref>relativeURI</x:ref>
     2035  <x:ref>Referer-v</x:ref>      = <x:ref>absolute-URI</x:ref> / <x:ref>partial-URI</x:ref>
    20362036</artwork></figure>
    20372037<t>
    … …  
    20432043<t>
    20442044   If the field value is a relative URI, it &SHOULD; be interpreted
    2045    relative to the Request-URI. The URI &MUST-NOT; include a fragment. See
     2045   relative to the request-target. The URI &MUST-NOT; include a fragment. See
    20462046   <xref target="encoding.sensitive.information.in.uris"/> for security considerations.
    20472047</t>
    … …  
    23872387   </c>
    23882388   <c>414</c>
    2389    <c>Request-URI Too Long</c>
     2389   <c>Request-target Too Long</c>
    23902390   <c>
    23912391      <xref target="status.414"/>
    … …  
    25922592   Authors of services should not use
    25932593   GET-based forms for the submission of sensitive data because that
    2594    data will be encoded in the Request-URI. Many existing
    2595    servers, proxies, and user agents log or display the Request-URI in
     2594   data will be encoded in the Request-target. Many existing
     2595   servers, proxies, and user agents log or display the Request-target in
    25962596   places where it might be visible to third parties. Such services can
    25972597   use POST-based form submission instead.
Note: See TracChangeset for help on using the changeset viewer.