W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2013

Re: #496, was: p6: Warning header field

From: Julian Reschke <julian.reschke@gmx.de>
Date: Mon, 23 Sep 2013 16:23:49 +0200
Message-ID: <52404EF5.50700@gmx.de>
To: "Roy T. Fielding" <fielding@gbiv.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2013-09-23 15:02, Julian Reschke wrote:
> ...
> I agree we need examples; I'll work on a proposal (ticket:
> http://trac.tools.ietf.org/wg/httpbis/trac/ticket/496)
>
> Best regards, Julian
> ...

Proposal 
(<http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/496/496.diff>):

5.5.8.  Examples

    A response message carrying a warning that indicates that the payload
    has been re-encoded (note the use of escaping in the quoted-string
    syntax):

      HTTP/1.1 200 OK
      Date: Sat, 25 Aug 2012 23:34:45 GMT
      Warning: 214 example.org "charset changed to \"iso-8859-1\""
       "Sat, 25 Aug 2012 23:34:45 GMT"
      Content-Type: text/plain; charset=iso-8859-1


    In the example below, the first warning-value carries a warn-date not
    matching the Date header field's value, and thus would be removed/
    ignored by the recipient:

      HTTP/1.1 200 OK
      Date: Sun, 26 Aug 2012 01:12:34 GMT
      Warning: 214 example.org "charset changed to \"iso-8859-1\""
       "Sat, 25 Aug 2012 23:34:45 GMT",
       214 example.org "charset changed to \"utf-8\""
       "Sun, 26 Aug 2012 01:12:34 GMT"
      Content-Type: text/plain; charset=utf-8


    In the examples above, line breaks (OWS) have been inserted into
    field values for readability (but see Section 3.2.4 of [Part1]).


Best regards, Julian
Received on Monday, 23 September 2013 14:24:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:15 UTC