Ignore:
Timestamp:
Dec 31, 2012, 3:51:04 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) that vs which

File:
1 edited

Legend:

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

    r2073 r2074  
    13401340</t>
    13411341<t>
    1342    If one or more resources has been created on the origin server, the response
    1343    &SHOULD; be <x:ref>201 (Created)</x:ref>, contain a representation which
    1344    describes the status of the request and refers to the new resource(s), and
    1345    include a <x:ref>Location</x:ref> header field that provides an identifier
    1346    for the primary resource created (see <xref target="header.location"/>).
     1342   If one or more resources has been created on the origin server, the origin
     1343   server &SHOULD; send a <x:ref>201 (Created)</x:ref> response containing a
     1344   <x:ref>Location</x:ref> header field that provides an identifier for the
     1345   primary resource created (<xref target="header.location"/>) and a
     1346   representation that describes the status of the request and refers to the
     1347   new resource(s).
    13471348</t>
    13481349<t>
    13491350   Responses to POST requests are only cacheable when they include explicit
    1350    freshness information (see &p6-explicit;). A cached POST response with a
    1351    <x:ref>Content-Location</x:ref> header field (see
    1352    &header-content-location;) whose value is the effective Request URI &MAY;
    1353    be used to satisfy subsequent GET and HEAD (not POST) requests.
     1351   freshness information (see &p6-explicit;). A cache &MUST-NOT; use a cached
     1352   POST response to satisfy a subsequent GET or HEAD request unless the
     1353   response contains a <x:ref>Content-Location</x:ref> header field with the
     1354   same value as the POST's effective request URI (&header-content-location;).
    13541355</t>
    13551356<t>
     
    13931394<t>
    13941395   An origin server &SHOULD; verify that the PUT representation is
    1395    consistent with any constraints which the server has for the target
     1396   consistent with any constraints the server has for the target
    13961397   resource that cannot or will not be changed by the PUT.  This is
    13971398   particularly important when the origin server uses internal
     
    14601461   A PUT request applied to the target resource &MAY; have side-effects
    14611462   on other resources.  For example, an article might have a URI for
    1462    identifying "the current version" (a resource) which is separate
     1463   identifying "the current version" (a resource) that is separate
    14631464   from the URIs identifying each particular version (different
    14641465   resources that at one point shared the same state as the current version
     
    16001601</t>
    16011602<t>
    1602    An origin server which receives a CONNECT request for itself &MAY;
     1603   An origin server that receives a CONNECT request for itself &MAY;
    16031604   respond with a <x:ref>2xx</x:ref> status code to indicate that a connection
    16041605   is established.  However, most origin servers do not implement CONNECT.
     
    17411742   methods to limit the number of times that the request is forwarded by
    17421743   proxies. This can be useful when the client is attempting to
    1743    trace a request which appears to be failing or looping mid-chain.
     1744   trace a request that appears to be failing or looping mid-chain.
    17441745</t>
    17451746<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Max-Forwards"/>
     
    18601861   Requirements for HTTP/1.1 origin servers:
    18611862  <list style="symbols">
    1862     <t> Upon receiving a request which includes an <x:ref>Expect</x:ref> header
     1863    <t> Upon receiving a request that includes an <x:ref>Expect</x:ref> header
    18631864        field with the "100-continue" expectation, an origin server &MUST;
    18641865        either respond with <x:ref>100 (Continue)</x:ref> status code and
     
    20992100   The media type quality factor associated with a given type is
    21002101   determined by finding the media range with the highest precedence
    2101    which matches that type. For example,
     2102   that matches the type. For example,
    21022103</t>
    21032104<figure><artwork type="example">
     
    21202121   &Note; A user agent might be provided with a default set of quality
    21212122   values for certain media ranges. However, unless the user agent is
    2122    a closed system which cannot interact with other rendering agents,
     2123   a closed system that cannot interact with other rendering agents,
    21232124   this default set ought to be configurable by the user.
    21242125</t>
     
    21332134   This field allows user agents capable of understanding more comprehensive
    21342135   or special-purpose charsets to signal that capability to an origin server
    2135    which is capable of representing documents in those charsets.
     2136   that is capable of representing documents in those charsets.
    21362137</t>
    21372138<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Accept-Charset"/>
     
    21492150<t>
    21502151   The special value "*", if present in the Accept-Charset field,
    2151    matches every charset which is not mentioned elsewhere in the
     2152   matches every charset that is not mentioned elsewhere in the
    21522153   Accept-Charset field. If no "*" is present in an Accept-Charset field,
    21532154   then any charsets not explicitly mentioned in the field are
     
    21872188</artwork></figure>
    21882189<t>
    2189    Each codings value &MAY; be given an associated quality value which
    2190    represents the preference for that encoding, as defined in &qvalue;.
     2190   Each codings value &MAY; be given an associated quality value
     2191   representing the preference for that encoding, as defined in &qvalue;.
    21912192</t>
    21922193<t>
     
    22582259</artwork></figure>
    22592260<t>
    2260    Each language-range can be given an associated quality value which
    2261    represents an estimate of the user's preference for the languages
     2261   Each language-range can be given an associated quality value
     2262   representing an estimate of the user's preference for the languages
    22622263   specified by that range, as defined in &qvalue;. For example,
    22632264</t>
     
    26652666   a change in the application protocol being used on this connection. The
    26662667   server will switch to the protocol(s) indicated within the response's
    2667    Upgrade header field immediately after the empty line which terminates the
     2668   Upgrade header field immediately after the empty line that terminates the
    26682669   101 response.
    26692670</t>
     
    32043205<t>
    32053206   The <x:dfn>406 (Not Acceptable)</x:dfn> status code indicates that the
    3206    <x:ref>target resource</x:ref> does not have a current representation which
     3207   <x:ref>target resource</x:ref> does not have a current representation that
    32073208   would be acceptable to the user agent, according to the
    32083209   <x:ref>proactive negotiation</x:ref> header fields received in the request
     
    32523253   Conflicts are most likely to occur in response to a PUT request. For
    32533254   example, if versioning were being used and the representation being PUT
    3254    included changes to a resource which conflict with those made by an
     3255   included changes to a resource that conflict with those made by an
    32553256   earlier (third-party) request, the origin server might use a 409 response
    32563257   to indicate that it can't complete the request. In this case, the response
     
    34033404<t>
    34043405   The <x:dfn>500 (Internal Server Error)</x:dfn> status code indicates that
    3405    the server encountered an unexpected condition which prevented it from
     3406   the server encountered an unexpected condition that prevented it from
    34063407   fulfilling the request.
    34073408</t>
     
    47614762   The <x:ref>User-Agent</x:ref> (<xref target="header.user-agent"/>) or
    47624763   <x:ref>Server</x:ref> (<xref target="header.server"/>) header fields can
    4763    sometimes be used to determine that a specific client or server has a
    4764    particular security hole which might be exploited. Unfortunately, this same
     4764   sometimes be used to determine if a specific client or server is more
     4765   likely to be vulnerable to a known security hole. Unfortunately, this same
    47654766   information is often used for other valuable purposes for which HTTP
    47664767   currently has no better mechanism.
     
    48344835<t>
    48354836   Accept header fields can reveal information about the user to all
    4836    servers which are accessed. The <x:ref>Accept-Language</x:ref> header field
     4837   servers that are accessed. The <x:ref>Accept-Language</x:ref> header field
    48374838   in particular can reveal information the user would consider to be of a
    48384839   private nature, because the understanding of particular languages is often
    48394840   strongly correlated to the membership of a particular ethnic group.
    4840    User agents which offer the option to configure the contents of an
     4841   User agents that offer the option to configure the contents of an
    48414842   Accept-Language header field to be sent in every request are strongly
    48424843   encouraged to let the configuration process include a message which
     
    48644865   header field configuration options to end users. As an extreme privacy
    48654866   measure, proxies could filter the accept header fields in relayed requests.
    4866    General purpose user agents which provide a high degree of header field
     4867   General purpose user agents that provide a high degree of header field
    48674868   configurability &SHOULD; warn users about the loss of privacy which can
    48684869   be involved.
     
    56485649   environment &SHOULD; translate all line breaks within the text media
    56495650   types described in <xref target="canonicalization.and.text.defaults"/>
    5650    of this document to the RFC 2049 canonical form of CRLF. Note, however, that
     5651   of this document to the RFC 2049 canonical form of CRLF. Note, however,
    56515652   this might be complicated by the presence of a <x:ref>Content-Encoding</x:ref>
    56525653   and by the fact that HTTP allows the use of some charsets
    5653    which do not use octets 13 and 10 to represent CR and LF, respectively.
     5654   that do not use octets 13 and 10 to represent CR and LF, respectively.
    56545655</t>
    56555656<t>
     
    57075708<section title="MHTML and Line Length Limitations" anchor="mhtml.line.length">
    57085709<t>
    5709    HTTP implementations which share code with MHTML <xref target="RFC2557"/> implementations
     5710   HTTP implementations that share code with MHTML <xref target="RFC2557"/> implementations
    57105711   need to be aware of MIME line length limitations. Since HTTP does not
    57115712   have this limitation, HTTP does not fold long lines. MHTML messages
Note: See TracChangeset for help on using the changeset viewer.