HTTPBis Summary Mark Nottingham (Wednesday, 26 March)
RE: PROPOSAL: i74: Encoding for non-ASCII headers Robert Brewer (Wednesday, 26 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Martin Duerst (Thursday, 27 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham (Thursday, 27 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Martin Duerst (Thursday, 27 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham (Thursday, 27 March)
- RE: PROPOSAL: i74: Encoding for non-ASCII headers Robert Brewer (Thursday, 27 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Thursday, 27 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham (Thursday, 27 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Friday, 28 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Frank Ellermann (Friday, 28 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Friday, 28 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Frank Ellermann (Friday, 28 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Saturday, 29 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Roy T. Fielding (Saturday, 29 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Robert Sayre (Saturday, 29 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Stefan Eissing (Saturday, 29 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Julian Reschke (Saturday, 29 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Henrik Nordstrom (Monday, 31 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Julian Reschke (Monday, 31 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers David Morris (Monday, 31 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Julian Reschke (Monday, 31 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Henrik Nordstrom (Monday, 31 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Julian Reschke (Monday, 31 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Frank Ellermann (Monday, 31 March)
- Re: PROPOSAL: i74: Encoding for non-ASCII headers Henrik Nordstrom (Monday, 31 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Roy T. Fielding (Monday, 31 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Henrik Nordstrom (Monday, 31 March)
UTF-8 (was: PROPOSAL: i74: Encoding for non-ASCII headers) Frank Ellermann (Monday, 31 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Stefan Eissing (Friday, 28 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Friday, 28 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Stefan Eissing (Friday, 28 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Friday, 28 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Stefan Eissing (Friday, 28 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Friday, 28 March)
Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier (Friday, 28 March)
HttpOnly Jim Manico (Tuesday, 18 March)
HTTPBIS Summary Mark Nottingham (Monday, 17 March)
Re: PROPOSAL: i24 Requiring Allow in 405 Responses Robert Siemer (Monday, 17 March)
Re: PROPOSAL: i24 Requiring Allow in 405 Responses Henrik Nordstrom (Tuesday, 18 March)
HTTPBIS Summary Mark Nottingham (Tuesday, 11 March)
Re: PROPOSAL: Weak Validator definition [i101] Henrik Nordstrom (Tuesday, 18 March)
Re: PROPOSAL: Weak Validator definition [i101] Mark Nottingham (Tuesday, 25 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Mark Nottingham (Monday, 10 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Monday, 10 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Harry Halpin (Monday, 10 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Harry Halpin (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Harry Halpin (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Harry Halpin (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Roy T. Fielding (Tuesday, 11 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Wednesday, 12 March)
- RE: Reviving HTTP Header Linking: Some code and use-cases Brian Smith (Wednesday, 12 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Wednesday, 12 March)
- RE: Reviving HTTP Header Linking: Some code and use-cases Brian Smith (Wednesday, 12 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Wednesday, 12 March)
- RE: Reviving HTTP Header Linking: Some code and use-cases Brian Smith (Wednesday, 12 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Roy T. Fielding (Wednesday, 12 March)
- RE: Reviving HTTP Header Linking: Some code and use-cases Brian Smith (Thursday, 13 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Thursday, 13 March)
- RE: Reviving HTTP Header Linking: Some code and use-cases Brian Smith (Thursday, 13 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Julian Reschke (Thursday, 13 March)
- RE: Reviving HTTP Header Linking: Some code and use-cases Martin Duerst (Friday, 14 March)
- IRIs, IDNAbis, and HTTP (was: Reviving HTTP Header Linking: Some code and use-cases) Frank Ellermann (Thursday, 13 March)
- RE: IRIs, IDNAbis, and HTTP (was: Reviving HTTP Header Linking: Some code and use-cases) Brian Smith (Thursday, 13 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Thursday, 13 March)
- RE: IRIs, IDNAbis, and HTTP Brian Smith (Thursday, 13 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Thursday, 13 March)
- RE: IRIs, IDNAbis, and HTTP Brian Smith (Thursday, 13 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Thursday, 13 March)
- RE: IRIs, IDNAbis, and HTTP Brian Smith (Thursday, 13 March)
- RE: IRIs, IDNAbis, and HTTP Martin Duerst (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Mark Nottingham (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Mark Nottingham (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Stefan Eissing (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Frank Ellermann (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Stefan Eissing (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Frank Ellermann (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Julian Reschke (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Frank Ellermann (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Martin Duerst (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Frank Ellermann (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Phil Archer (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Mark Nottingham (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Anne van Kesteren (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Anne van Kesteren (Monday, 17 March)
- Link header field titles (was: IRIs, IDNAbis, and HTTP) Frank Ellermann (Monday, 17 March)
- Re: Link header field titles Julian Reschke (Monday, 17 March)
- Re: Link header field titles Julian Reschke (Monday, 17 March)
- Re: Link header field titles Martin Duerst (Tuesday, 18 March)
- Re: Link header field titles Julian Reschke (Tuesday, 18 March)
- Re: IRIs, IDNAbis, and HTTP Stefan Eissing (Friday, 14 March)
- RE: IRIs, IDNAbis, and HTTP Brian Smith (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Friday, 14 March)
- RE: IRIs, IDNAbis, and HTTP Brian Smith (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Friday, 14 March)
- RE: IRIs, IDNAbis, and HTTP [i74] Brian Smith (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Frank Ellermann (Saturday, 15 March)
- RE: IRIs, IDNAbis, and HTTP [i74] Brian Smith (Saturday, 15 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Frank Ellermann (Saturday, 15 March)
- Content-Disposition filename encoding, was: IRIs, IDNAbis, and HTTP [i74] Julian Reschke (Sunday, 16 March)
- Re: Content-Disposition filename encoding, was: IRIs, IDNAbis, and HTTP [i74] Julian Reschke (Sunday, 16 March)
- Re: Content-Disposition filename encoding Frank Ellermann (Sunday, 16 March)
- Re: Content-Disposition filename encoding Julian Reschke (Monday, 17 March)
- Re: Content-Disposition filename encoding Frank Ellermann (Monday, 17 March)
- Re: Content-Disposition filename encoding Julian Reschke (Monday, 17 March)
- Re: Content-Disposition filename encoding Frank Ellermann (Monday, 24 March)
- Re: Content-Disposition filename encoding Julian Reschke (Monday, 24 March)
- Re: Content-Disposition filename encoding Frank Ellermann (Monday, 24 March)
- Re: Content-Disposition filename encoding Julian Reschke (Monday, 24 March)
- Re: Content-Disposition filename encoding, was: IRIs, IDNAbis, and HTTP [i74] Henrik Nordstrom (Tuesday, 18 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Martin Duerst (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP [i74] Frank Ellermann (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Friday, 14 March)
- RE: IRIs, IDNAbis, and HTTP Brian Smith (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Saturday, 15 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Julian Reschke (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Monday, 17 March)
- RE: IRIs, IDNAbis, and HTTP Paul Hoffman (Thursday, 13 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Thursday, 13 March)
- Re: IRIs, IDNAbis, and HTTP Martin Duerst (Friday, 14 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Monday, 17 March)
- Re: IRIs, IDNAbis, and HTTP Henrik Nordstrom (Tuesday, 18 March)
- Re: IRIs, IDNAbis, and HTTP Frank Ellermann (Tuesday, 18 March)
- Re: Reviving HTTP Header Linking: Some code and use-cases Harry Halpin (Wednesday, 12 March)
RE: Reviving HTTP Header Linking: Some code and use-cases Brian Smith (Wednesday, 12 March)
Re: Reviving HTTP Header Linking: Some code and use-cases Mark Nottingham (Friday, 14 March)
Connection limits Mark Nottingham (Wednesday, 5 March)
HTTPBIS Summary Mark Nottingham (Monday, 3 March)
RE: i107 Brian Smith (Thursday, 28 February)
- RE: i107 Brian Smith (Thursday, 28 February)
- RE: i107 Henrik Nordstrom (Thursday, 13 March)
- RE: i107 Brian Smith (Friday, 14 March)
- RE: i107 Henrik Nordstrom (Friday, 14 March)
BIS -02 Drafts Mark Nottingham (Tuesday, 26 February)
Re: PATCH vs multipart/byteranges vs Content-Range Mark Nottingham (Thursday, 28 February)
Re: PATCH vs multipart/byteranges vs Content-Range Julian Reschke (Saturday, 16 February)
Re: PATCH vs multipart/byteranges vs Content-Range Subbu Allamaraju (Saturday, 16 February)
Re: PATCH vs multipart/byteranges vs Content-Range Roy T. Fielding (Saturday, 16 February)
Re: PATCH vs multipart/byteranges vs Content-Range Adrien de Croy (Saturday, 16 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Thursday, 28 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses Julian Reschke (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses John Kemp (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses Julian Reschke (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses John Kemp (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses Julian Reschke (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses Roy T. Fielding (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses Julian Reschke (Tuesday, 4 March)
- Re: i24: Requiring Allow in 405 responses Henrik Nordstrom (Friday, 14 March)
Re: i24: Requiring Allow in 405 responses Julian Reschke (Friday, 29 February)
Re: i24: Requiring Allow in 405 responses Henrik Nordstrom (Thursday, 13 March)
i76: 305 Use Proxy Mark Nottingham (Wednesday, 13 February)
- Re: i24: Requiring Allow in 405 responses Mark Baker (Tuesday, 5 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Tuesday, 5 February)
- Re: i24: Requiring Allow in 405 responses Henrik Nordström (Tuesday, 5 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Tuesday, 5 February)
- Re: i24: Requiring Allow in 405 responses Henrik Nordström (Tuesday, 5 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Tuesday, 5 February)
- Re: i24: Requiring Allow in 405 responses Henrik Nordström (Wednesday, 6 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Wednesday, 13 February)
- Re: i24: Requiring Allow in 405 responses Mark Baker (Wednesday, 13 February)
- Re: i24: Requiring Allow in 405 responses Robert Sayre (Wednesday, 13 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Wednesday, 13 February)
- Re: i24: Requiring Allow in 405 responses Mark Nottingham (Wednesday, 13 February)
- Re: i24: Requiring Allow in 405 responses Robert Sayre (Wednesday, 13 February)
- Re: i24: Requiring Allow in 405 responses Julian Reschke (Thursday, 14 February)
- Re: i24: Requiring Allow in 405 responses Julian Reschke (Thursday, 14 February)
- Re: i24: Requiring Allow in 405 responses Roy T. Fielding (Thursday, 14 February)
Re: i24: Requiring Allow in 405 responses Roy T. Fielding (Tuesday, 5 February)
Re: i24: Requiring Allow in 405 responses Robert Sayre (Friday, 7 March)
- Re: HTML5 vs content type sniffing Frank Ellermann (Friday, 25 January)
- Re: HTML5 vs content type sniffing Julian Reschke (Friday, 25 January)
- Re: HTML5 vs content type sniffing Robert Siemer (Friday, 25 January)
- Re: HTML5 vs content type sniffing Frank Ellermann (Saturday, 26 January)
- Re: HTML5 vs content type sniffing Ian Hickson (Monday, 28 January)
- Re: HTML5 vs content type sniffing Robert Siemer (Tuesday, 29 January)
- Re: HTML5 vs content type sniffing Robert Siemer (Tuesday, 29 January)
- Re: HTML5 vs content type sniffing Ian Hickson (Wednesday, 30 January)
- Re: HTML5 vs content type sniffing Julian Reschke (Saturday, 2 February)
- Re: HTML5 vs content type sniffing Ian Hickson (Saturday, 2 February)
- Re: HTML5 vs content type sniffing Julian Reschke (Saturday, 2 February)
- Re: HTML5 vs content type sniffing Ian Hickson (Saturday, 2 February)
- Re: HTML5 vs content type sniffing Julian Reschke (Saturday, 2 February)
- Re: HTML5 vs content type sniffing Ian Hickson (Saturday, 2 February)
- Re: HTML5 vs content type sniffing David Morris (Monday, 4 February)
Re: HTML5 vs content type sniffing Julian Reschke (Saturday, 2 February)
SRV records for HTTP Stephane Bortzmeyer (Friday, 11 January)
http over sctp? Adrian Chadd (Wednesday, 9 January)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Roy T. Fielding (Thursday, 10 January)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Mark Nottingham (Wednesday, 30 January)
- RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 31 January)
- RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Yves Lafon (Thursday, 31 January)
- RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 31 January)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Thursday, 31 January)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Yves Lafon (Thursday, 31 January)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Mark Nottingham (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Stefan Eissing (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Yves Lafon (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Yves Lafon (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Henrik Nordström (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Henrik Nordström (Tuesday, 5 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Subbu Allamaraju (Monday, 25 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Mark Nottingham (Tuesday, 26 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Subbu Allamaraju (Thursday, 28 February)
Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Henrik Nordström (Tuesday, 5 February)
Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Mark Nottingham (Wednesday, 13 February)
RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Wednesday, 13 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Thursday, 14 February)
- RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 14 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Thursday, 14 February)
- RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 14 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Thursday, 14 February)
- RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 14 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Thursday, 14 February)
- RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 14 February)
- Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Julian Reschke (Thursday, 14 February)
RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 14 February)
RE: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Brian Smith (Thursday, 14 February)
Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Mark Nottingham (Thursday, 28 February)
Re: i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND] Mark Nottingham (Thursday, 28 February)
Philidelphia Mark Nottingham (Tuesday, 8 January)
- Re: Unknown text/* subtypes Frank Ellermann (Tuesday, 8 January)
- Re: Unknown text/* subtypes [i20] Mark Nottingham (Wednesday, 9 January)
- RE: Unknown text/* subtypes [i20] Robert Brewer (Wednesday, 9 January)
- Re: Unknown text/* subtypes [i20] Julian Reschke (Tuesday, 12 February)
- Re: Unknown text/* subtypes [i20] Julian Reschke (Thursday, 14 February)
- Re: Unknown text/* subtypes [i20] Roy T. Fielding (Thursday, 14 February)
- PROCESS: Tracking design issues under discussion Mark Nottingham (Thursday, 14 February)
- Re: PROCESS: Tracking design issues under discussion Julian Reschke (Thursday, 14 February)
- Re: PROCESS: Tracking design issues under discussion Roy T. Fielding (Thursday, 14 February)
- Re: PROCESS: Tracking design issues under discussion Frank Ellermann (Friday, 15 February)
- Re: PROCESS: Tracking design issues under discussion Mark Nottingham (Tuesday, 19 February)
- Re: PROCESS: Tracking design issues under discussion Frank Ellermann (Tuesday, 19 February)
- RE: PROCESS: Tracking design issues under discussion Brian Smith (Wednesday, 27 February)
- Re: PROCESS: Tracking design issues under discussion Julian Reschke (Wednesday, 27 February)
- Re: PROCESS: Tracking design issues under discussion Mark Nottingham (Wednesday, 27 February)
- Re: Unknown text/* subtypes [i20] Frank Ellermann (Thursday, 14 February)
- Re: Unknown text/* subtypes [i20] Roy T. Fielding (Friday, 15 February)
- Re: Unknown text/* subtypes [i20] Frank Ellermann (Friday, 15 February)
- Re: Unknown text/* subtypes [i20] Mark Nottingham (Tuesday, 11 March)
- Re: Unknown text/* subtypes [i20] Frank Ellermann (Tuesday, 11 March)
- Default charsets for text media types [i20] Mark Nottingham (Tuesday, 25 March)
- Re: Default charsets for text media types [i20] Simon Perreault (Tuesday, 25 March)
- Re: Default charsets for text media types [i20] Frank Ellermann (Tuesday, 25 March)
- Re: Default charsets for text media types [i20] Martin Duerst (Wednesday, 26 March)
- Re: Default charsets for text media types [i20] Frank Ellermann (Wednesday, 26 March)
- Re: Default charsets for text media types [i20] Martin Duerst (Thursday, 27 March)
- OT: History (was: Re: Default charsets for text media types [i20]) Martin Duerst (Thursday, 27 March)
- Re: Default charsets for text media types [i20] Henrik Nordstrom (Tuesday, 25 March)
- Re: Default charsets for text media types [i20] Martin Duerst (Wednesday, 26 March)
Re: Unknown text/* subtypes [i20] Geoffrey Sneddon (Tuesday, 12 February)
Re: Unknown text/* subtypes [i20] Albert Lunde (Tuesday, 12 February)
Re: Unknown text/* subtypes [i20] Frank Ellermann (Tuesday, 12 February)
Re: Unknown text/* subtypes Geoffrey Sneddon (Thursday, 10 January)
- text/* types and charset defaults Larry Masinter (Sunday, 13 January)
- Re: text/* types and charset defaults Julian Reschke (Sunday, 20 January)
- Re: text/* types and charset defaults Frank Ellermann (Sunday, 20 January)
- Re: text/* types and charset defaults [i20] Mark Nottingham (Tuesday, 22 January)
- Re: text/* types and charset defaults [i20] Julian Reschke (Tuesday, 22 January)
- security impact of dropping charset default [Re: text/* types and charset defaults [i20]] Yutaka Oiwa (Wednesday, 23 January)
- Re: security impact of dropping charset default [Re: text/* types and charset defaults [i20]] Roy T. Fielding (Wednesday, 23 January)
- Re: security impact of dropping charset default [Re: text/* types and charset defaults [i20]] Yutaka Oiwa (Wednesday, 23 January)
- Re: security impact of dropping charset default Frank Ellermann (Wednesday, 23 January)
- Re: security impact of dropping charset default Anne van Kesteren (Wednesday, 23 January)
- Re: security impact of dropping charset default Julian Reschke (Wednesday, 23 January)
- Re: security impact of dropping charset default Anne van Kesteren (Wednesday, 23 January)
- Re: security impact of dropping charset default David Morris (Wednesday, 23 January)
- Re: security impact of dropping charset default Julian Reschke (Wednesday, 23 January)
- Re: security impact of dropping charset default Roy T. Fielding (Wednesday, 23 January)
- Re: security impact of dropping charset default Julian Reschke (Wednesday, 23 January)
- Re: security impact of dropping charset default Frank Ellermann (Wednesday, 23 January)
- Re: security impact of dropping charset default Roy T. Fielding (Wednesday, 23 January)
- Re: security impact of dropping charset default Adrien de Croy (Wednesday, 23 January)
- Re: security impact of dropping charset default Mark Nottingham (Thursday, 24 January)
- Re: security impact of dropping charset default Adrien de Croy (Thursday, 24 January)
- "HTTP for Web Browsers and Servers" Larry Masinter (Thursday, 24 January)
- Re: "HTTP for Web Browsers and Servers" Geoffrey Sneddon (Thursday, 24 January)
- RE: "HTTP for Web Browsers and Servers" Larry Masinter (Friday, 25 January)
- Re: "HTTP for Web Browsers and Servers" Mark Nottingham (Wednesday, 30 January)
- Re: security impact of dropping charset default Mark Nottingham (Wednesday, 30 January)
- Re: security impact of dropping charset default Yves Lafon (Thursday, 24 January)
- Re: security impact of dropping charset default Henrik Nordström (Tuesday, 5 February)
- Re: security impact of dropping charset default Mark Nottingham (Tuesday, 5 February)
Re: security impact of dropping charset default Frank Ellermann (Wednesday, 23 January)
Re: security impact of dropping charset default Anne van Kesteren (Wednesday, 23 January)
Re: security impact of dropping charset default James Graham (Wednesday, 23 January)
Re: security impact of dropping charset default [Re: text/* types and charset defaults [i20]] Julian Reschke (Wednesday, 23 January)
Re: Unknown text/* subtypes Ian Hickson (Sunday, 13 January)
Re: Re: Unknown text/* subtypes Ned Freed (Monday, 14 January)
Re: Unknown text/* subtypes Ian Hickson (Tuesday, 15 January)
Re: i22: ETags on PUT responses Henrik Nordstrom (Saturday, 5 January)
Updated Patch James M Snell (Thursday, 3 January)
Last message date: Monday, 31 March 2008 21:21:22 UTC