Changeset 1069 for draft-ietf-httpbis/latest/p1-messaging.xml

Timestamp:

Oct 28, 2010, 6:24:45 AM (9 years ago)

Author:

julian.reschke@…

Message:

make the comment about redirection status codes less specific (for instance, we deprecated 305 for issue #76)

File:

• draft-ietf-httpbis/latest/p1-messaging.xml (modified) (2 diffs)

draft-ietf-httpbis/latest/p1-messaging.xml

@@ -35 +35 @@
   <!ENTITY status-100             "<xref target='Part2' x:rel='#status.100' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-1xx             "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
+  <!ENTITY status-3xx             "<xref target='Part2' x:rel='#status.3xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
   <!ENTITY status-414             "<xref target='Part2' x:rel='#status.414' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
 ]>
@@ -3292 +3293 @@
    The Upgrade header field cannot be used to indicate a switch to a
    protocol on a different connection. For that purpose, it is more
-   appropriate to use a 301, 302, 303, or 305 redirection response.
+   appropriate to use a 3xx redirection response (&status-3xx;).
 </t>
 <t>