#496 closed editorial (incorporated)
add Warning header field examples
Reported by: | julian.reschke@… | Owned by: | julian.reschke@… |
---|---|---|---|
Priority: | normal | Milestone: | 24 |
Component: | p6-cache | Severity: | In WG Last Call |
Keywords: | Cc: |
Description
Quoting <http://www.w3.org/mid/413C419A-AE9D-46F8-82A5-72B4341754AD@gbiv.com>:
I just noticed that the definition of the Warning header field includes a required host or pseudonym between the warn-code and the warn-text, and further that the warn-text is a quoted-string.
Since there are no examples provided, and the table of warn-codes makes them look like status-code reason-phrase, it should be no surprise that implementations send things like
Warning: 110 Response is stale Warning: 110 squid/3.2.0.5 "Response is stale" Warning: 111 squid/3.2.0.5 "Revalidation failed" Warning: 111 Revalidation failed Warning: 112 Disconnected Operation Warning: 214 host.example.com Transformation applied
In fact, the only places I can find correctly formatted Warning header fields is in an internal Apache debugging module (mod_policy, abusing that field for other means) and within a BEA example for SIP.
Warning: 307 isi.edu "Session parameter 'foo' not understood"
(...)
Attachments (1)
Change History (7)
comment:1 Changed 9 years ago by julian.reschke@…
- Owner changed from draft-ietf-httpbis-p6-cache@… to julian.reschke@…
Changed 9 years ago by julian.reschke@…
comment:2 Changed 9 years ago by fielding@…
Thanks, but those examples are more extensive than needed. A warn-date serves no purpose on a 214.
I already made the section headers look like valid examples (without warn-date); I will add one example with a warn-date.
comment:3 Changed 9 years ago by fielding@…
comment:4 Changed 9 years ago by fielding@…
- Resolution set to incorporated
- Status changed from new to closed
comment:5 Changed 9 years ago by fielding@…
- Milestone changed from unassigned to 24
proposed examples section