ietf-http-wg@w3.org from July to September 2009 by date

Wednesday, 30 September 2009

Re: Header encoding (per RFC2231), was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Header encoding (per RFC2231), was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson
Re: Header encoding (per RFC2231), was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Header encoding (per RFC2231), was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson
Header encoding (per RFC2231), was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson

Tuesday, 29 September 2009

Meaning of Location header in 204 Responses Jan Algermissen
Instance Digests in HTTP (RFC3230) Anthony Bryan

Monday, 28 September 2009

Re: Clarifying Content-Location (Issue 136) Julian Reschke
Re: Clarifying Content-Location (Issue 136) Roy T. Fielding
RE: Clarifying Content-Location (Issue 136) Brian Smith
Re: Clarifying Content-Location (Issue 136) Julian Reschke
Re: Issue 194: restricting allowed characters in quoted-pair Julian Reschke
RE: Clarifying Content-Location (Issue 136) Brian Smith
Re: Clarifying Content-Location (Issue 136) Adrien de Croy

Sunday, 27 September 2009

Re: Issue 194: restricting allowed characters in quoted-pair Roy T. Fielding
RE: Clarifying Content-Location (Issue 136) Robert Brewer
Re: Issue 194: restricting allowed characters in quoted-pair Henrik Nordstrom
Re: Clarifying Content-Location (Issue 136) Julian Reschke
RE: Clarifying Content-Location (Issue 136) Robert Brewer
Clarifying Content-Location (Issue 136) Julian Reschke
Re: Issue 194: restricting allowed characters in quoted-pair Julian Reschke
Re: Input on request for link relation Mark Nottingham

Saturday, 26 September 2009

Re: Multi-server HTTP Mark Nottingham
Re: header parsing, trailing OWS David Morris
Re: header parsing, trailing OWS Julian Reschke
Re: header parsing, trailing OWS Jamie Lokier

Friday, 25 September 2009

Re: Multi-server HTTP Henrik Nordstrom
Re: Multi-server HTTP Anthony Bryan
Re: Issue 194: restricting allowed characters in quoted-pair Henrik Nordstrom
Re: Issue 194: restricting allowed characters in quoted-pair Julian Reschke
Re: Issue 194: restricting allowed characters in quoted-pair Henrik Nordstrom
Re: Issue 194: restricting allowed characters in quoted-pair Sam Johnston
Re: Issue 194: restricting allowed characters in quoted-pair Julian Reschke
Re: Issue 194: restricting allowed characters in quoted-pair Sam Johnston
Re: Issue 194: restricting allowed characters in quoted-pair Julian Reschke
Re: HTTP 2.0 (was Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard) Julian Reschke
HTTP 2.0 (was Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard) Sam Johnston
IETF patent policy Lisa Dusseault
OpenSearch 'search' link relation Jan Algermissen
RE: Multi-server HTTP Nicolas Alvarez
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham

Thursday, 24 September 2009

Re: CORS redirect behavior proposal Adam Barth
RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav
Re: header parsing, trailing OWS David Morris
Re: Fwd: New Version Notification for draft-murata-kohn-lilley-xml-03 Julian Reschke
Re: CORS redirect behavior proposal Anne van Kesteren
header parsing, trailing OWS Julian Reschke
RE: Multi-server HTTP Ford, Alan
Re: CORS redirect behavior proposal Anne van Kesteren
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Input on request for link relation Ian Hickson
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson

Wednesday, 23 September 2009

Re: CORS redirect behavior proposal Adam Barth
draft agenda for IRI working group BOF, and draft charter for IRI Larry Masinter
Re: CORS redirect behavior proposal Anne van Kesteren
Re: [OAUTH-WG] OAuth and HTTP caching John Panzer
Re: [OAUTH-WG] OAuth and HTTP caching Peter Saint-Andre
Re: [OAUTH-WG] OAuth and HTTP caching Mark Nottingham
Re: [OAUTH-WG] OAuth and HTTP caching Phillip Hallam-Baker

Tuesday, 22 September 2009

RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson
CORS redirect behavior proposal Collin Jackson
Re: [OAUTH-WG] OAuth and HTTP caching Roy T. Fielding
RE: [OAUTH-WG] OAuth and HTTP caching Eran Hammer-Lahav
Re: [OAUTH-WG] OAuth and HTTP caching Roy T. Fielding
Re: [OAUTH-WG] OAuth and HTTP caching John Panzer
Re: [OAUTH-WG] OAuth and HTTP caching Mark Nottingham

Monday, 21 September 2009

Re: [OAUTH-WG] OAuth and HTTP caching John Panzer

Tuesday, 22 September 2009

RE: OAuth and HTTP caching Eran Hammer-Lahav
Re: #197: Effect of CC directives on history lists Mark Nottingham
Re: OAuth and HTTP caching Mark Nottingham

Monday, 21 September 2009

OAuth and HTTP caching Eran Hammer-Lahav
RE: #197: Effect of CC directives on history lists Henrik Nordstrom
Re: Input on request for link relation [ w/ proposed modifications to link draft ] Robert Sayre
RE: #197: Effect of CC directives on history lists Brian Smith
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: #197: Effect of CC directives on history lists Henrik Nordstrom
Re: Input on request for link relation Sam Johnston
Re: Input on request for link relation Mark Nottingham
Re: Input on request for link relation [ w/ proposed modifications to link draft ] Brett Slatkin
Re: Input on request for link relation [ w/ proposed modifications to link draft ] Brett Slatkin
Re: Input on request for link relation [ w/ proposed modifications to link draft ] Brett Slatkin
Re: Input on request for link relation Brett Slatkin
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
RE: Input on request for link relation Eran Hammer-Lahav
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Anthony Bryan
Re: [httpbis] #81: Content Negotiation for media types Mark Nottingham
Re: Input on request for link relation [ w/ proposed modifications to link draft ] Mark Nottingham
Re: Input on request for link relation [ w/ proposed modifications to link draft ] Robert Sayre

Saturday, 19 September 2009

Re: #197: Effect of CC directives on history lists Mark Nottingham

Sunday, 20 September 2009

Saturday, 19 September 2009

Re: Multi-server HTTP Anthony Bryan
fyi: Strict Transport Security specification =JeffH

Friday, 18 September 2009

RE: [pubsubhubbub] Re: Input on request for link relation Eran Hammer-Lahav
Re: [pubsubhubbub] Re: Input on request for link relation Martin Atkins

Thursday, 17 September 2009

Re: [httpbis] #81: Content Negotiation for media types Martin J. Dürst
Re: Multi-server HTTP Sam Johnston
duplicate relation (was Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard) Sam Johnston
Re: #197: Effect of CC directives on history lists Henrik Nordstrom
Re: Issue 194: restricting allowed characters in quoted-pair Henrik Nordstrom
Re: Input on request for link relation [ w/ proposed modifications to link draft ] John Panzer
Re: Multi-server HTTP Anthony Bryan
Re: Input on request for link relation Sam Johnston
Re: [httpbis] #81: Content Negotiation for media types Julian Reschke
Re: Input on request for link relation Brett Slatkin
Re: Input on request for link relation Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav
Re: Input on request for link relation [ w/ proposed modifications to link draft ] Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: [httpbis] #81: Content Negotiation for media types Mark Nottingham
RE: Input on request for link relation Eran Hammer-Lahav
RE: Input on request for link relation Eran Hammer-Lahav
#197: Effect of CC directives on history lists Mark Nottingham
RE: [httpbis] #81: Content Negotiation for media types Larry Masinter
RE: Input on request for link relation Eran Hammer-Lahav
RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav

Wednesday, 16 September 2009

RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav
RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav

Tuesday, 15 September 2009

Re: [pubsubhubbub] Re: Input on request for link relation Brett Slatkin

Wednesday, 16 September 2009

Re: Input on request for link relation Brett Slatkin
IDNA, IRI, HTML5 coordination Larry Masinter
Re: Issue 194: restricting allowed characters in quoted-pair Julian Reschke
Re: #110: how to determine what entity a response carries Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Input on request for link relation Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Input on request for link relation Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson
Re: Multi-server HTTP Mark Nottingham
Re: Issue 194: restricting allowed characters in quoted-pair Mark Nottingham
Re: Issue 194: restricting allowed characters in quoted-pair Henrik Nordstrom
Re: Issue 194: restricting allowed characters in quoted-pair Roy T. Fielding
Re: Input on request for link relation Mark Nottingham
Re: Issue 194: restricting allowed characters in quoted-pair Mark Nottingham
Re: IANA Link Relations Registry (draft-nottingham-http-link-header) Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Input on request for link relation Mark Nottingham
Re: [draft-nottingham-http-link-header-06] rev Mark Nottingham
Re: #110: how to determine what entity a response carries Mark Nottingham

Tuesday, 15 September 2009

Re: Multi-server HTTP Anthony Bryan
Re: Multi-server HTTP Mark Nottingham

Friday, 11 September 2009

Re: Input on request for link relation John Panzer
Re: Input on request for link relation Adam Roach
Re: Input on request for link relation Peter Saint-Andre
Re: Input on request for link relation Kris Zyp
Re: Input on request for link relation Sam Johnston
Re: Input on request for link relation Peter Saint-Andre
Re: Input on request for link relation Kris Zyp
Re: Input on request for link relation Peter Saint-Andre
Re: Input on request for link relation Hadrien Gardeur
Re: Input on request for link relation Hadrien Gardeur
Re: Input on request for link relation Sam Johnston
Re: Input on request for link relation Kris Zyp
Re: Input on request for link relation Julian Reschke
defining "Request-URI", was: #110: how to determine what entity a response carries Julian Reschke
Re: Input on request for link relation Sam Johnston
Re: #110: how to determine what entity a response carries Julian Reschke
Re: #167: Content-Location on 304 responses Julian Reschke

Thursday, 10 September 2009

Re: Input on request for link relation Jan Algermissen
Re: Input on request for link relation John Panzer
Re: Input on request for link relation Jan Algermissen
Re: Input on request for link relation Robert Sayre
Input on request for link relation Lisa Dusseault

Wednesday, 9 September 2009

Re: Link Relations: up/down vs parent/child vs ancestor/descendant etc. Nikunj R. Mehta
Re: [draft-nottingham-http-link-header-06] concerns about Link header Anne van Kesteren

Tuesday, 8 September 2009

Link Relations: up/down vs parent/child vs ancestor/descendant etc. Sam Johnston
Re: Multi-server HTTP Anthony Bryan

Sunday, 6 September 2009

IANA Link Relations Registry (draft-nottingham-http-link-header) Sam Johnston

Thursday, 3 September 2009

Re: AW: Use of Status Code 500 Henrik Nordstrom
Re: AW: AW: Use of Status Code 500 David Morris
AW: AW: Use of Status Code 500 Svensson, Lars
Re: AW: Use of Status Code 500 Julian Reschke
AW: Use of Status Code 500 Svensson, Lars

Wednesday, 2 September 2009

Re: Use of Status Code 500 Henrik Nordstrom
Use of Status Code 500 Svensson, Lars

Tuesday, 1 September 2009

Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Joe Gregorio
Re: Multi-server HTTP Mark Nottingham
Re: [draft-nottingham-http-link-header-06] concerns about Link header Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: The HTTP Sec-From Header (draft-abarth-origin) Maciej Stachowiak
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: The HTTP Sec-From Header (draft-abarth-origin) Maciej Stachowiak
Re: Multi-server HTTP Nicolas Alvarez
Re: The HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: #167: Content-Location on 304 responses Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Multi-server HTTP Mark Nottingham

Monday, 31 August 2009

Re: Multi-server HTTP Anthony Bryan
Re: [draft-nottingham-http-link-header-06] concerns about Link header Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Nicolas Alvarez
Re: [draft-nottingham-http-link-header-06] concerns about Link header Nicolas Alvarez
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Nicolas Alvarez
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Al Brown
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Joe Gregorio
Re: #167: Content-Location on 304 responses Julian Reschke
Re: [draft-nottingham-http-link-header-06] concerns about Link header Sam Johnston
Re: [draft-nottingham-http-link-header-06] concerns about Link header Noah Slater
Re: [draft-nottingham-http-link-header-06] concerns about Link header Sam Johnston
Re: [draft-nottingham-http-link-header-06] concerns about Link header Michael Hausenblas
Re: [draft-nottingham-http-link-header-06] concerns about Link header Jan Algermissen
Re: [draft-nottingham-http-link-header-06] concerns about Link header Noah Slater
Re: [draft-nottingham-http-link-header-06] concerns about Link header Sam Johnston
Re: [draft-nottingham-http-link-header-06] concerns about Link header Noah Slater
Re: [draft-nottingham-http-link-header-06] concerns about Link header Julian Reschke
Re: [draft-nottingham-http-link-header-06] concerns about Link header Mike Burrows
[draft-nottingham-http-link-header-06] concerns about Link header Anne van Kesteren
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Multi-server HTTP Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: #167: Content-Location on 304 responses Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav

Sunday, 30 August 2009

Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: #167: Content-Location on 304 responses Julian Reschke
Re: Link: grandfathered format-specific registered relations Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson

Friday, 28 August 2009

RE: Multi-server HTTP Henrik Nordstrom
Re: Multi-server HTTP Anthony Bryan
RE: Multi-server HTTP Henrik Nordstrom
RE: Multi-server HTTP Daniel Stenberg
RE: Multi-server HTTP Ford, Alan
Issue 194: restricting allowed characters in quoted-pair Julian Reschke
Re: #173: CR and LF in chunk extension values Henrik Nordstrom
Re: #173: CR and LF in chunk extension values Roy T. Fielding

Thursday, 27 August 2009

Re: #173: CR and LF in chunk extension values Henrik Nordstrom
Re: #173: CR and LF in chunk extension values Julian Reschke
Re: #173: CR and LF in chunk extension values Henrik Nordstrom
Re: #173: CR and LF in chunk extension values Julian Reschke
RE: Multi-server HTTP : Robert Siemer

Wednesday, 26 August 2009

RE: Multi-server HTTP Henrik Nordstrom
RE: Review of Content-Encoding: value token [exi] John Schneider
RE: Review of Content-Encoding: value token [exi] John Schneider
Re: Review of Content-Encoding: value token [exi] Roy T. Fielding
Re: Review of Content-Encoding: value token [exi] Mark Nottingham
RE: Review of Content-Encoding: value token [exi] Henrik Nordstrom
Re: Review of Content-Encoding: value token [exi] Henrik Nordstrom
RE: Review of Content-Encoding: value token [exi] John Schneider
Re: Multi-server HTTP Anthony Bryan
Re: Review of Content-Encoding: value token [exi] Mark Nottingham

Tuesday, 25 August 2009

RE: Review of Content-Encoding: value token [exi] John Schneider
Re: #173: CR and LF in chunk extension values Henrik Nordstrom
Re: #173: CR and LF in chunk extension values Henrik Nordstrom
Re: #173: CR and LF in chunk extension values Julian Reschke
Re: #173: CR and LF in chunk extension values Julian Reschke
Re: #173: CR and LF in chunk extension values Henrik Nordstrom
Re: Review of Content-Encoding: value token [exi] Henrik Nordstrom
[draft-nottingham-http-link-header-06] processing requirements Anne van Kesteren
Re: [draft-nottingham-http-link-header-06] relation-types Julian Reschke
Re: [draft-nottingham-http-link-header-06] relation-types Anne van Kesteren
RE: Multi-server HTTP Ford, Alan
RE: Multi-server HTTP Ford, Alan
Re: [draft-nottingham-http-link-header-06] relation-types Sam Johnston
Re: [draft-nottingham-http-link-header-06] relation-types Julian Reschke
Re: [draft-nottingham-http-link-header-06] relation-types Anne van Kesteren
Re: [draft-nottingham-http-link-header-06] relation-types Julian Reschke
Re: [draft-nottingham-http-link-header-06] 4.1 Registered Relation Types Anne van Kesteren
Re: [draft-nottingham-http-link-header-06] relation-types Anne van Kesteren
Re: #173: CR and LF in chunk extension values Julian Reschke
Re: Multi-server HTTP : Robert Siemer
Re: Multi-server HTTP Mark Nottingham
Re: Review of Content-Encoding: value token [exi] Mark Nottingham
Re: #173: CR and LF in chunk extension values Mark Nottingham

Monday, 24 August 2009

RE: Review of Content-Encoding: value token [exi] John Schneider
RE: Review of Content-Encoding: value token [exi] Henrik Nordstrom
Re: [draft-nottingham-http-link-header-06] rev Roy T. Fielding
Re: Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Roy T. Fielding
RE: Review of Content-Encoding: value token [exi] John Schneider
Re: [draft-nottingham-http-link-header-06] rev Ian Hickson
Re: #173: CR and LF in chunk extension values Julian Reschke
Re: [draft-nottingham-http-link-header-06] rev Anne van Kesteren
Re: Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Julian Reschke
Re: Review of Content-Encoding: value token [exi] Henrik Nordstrom
Re: #169: private and no-cache CC directives w/ header args Henrik Nordstrom
Re: #184: HTTP/0.9 Julian Reschke
Re: [draft-nottingham-http-link-header-06] rev Ian Hickson
Re: #184: HTTP/0.9 Mark Nottingham
Re: Review of Content-Encoding: value token [exi] John Schneider
Re: #173: CR and LF in chunk extension values Mark Nottingham
Re: Trailers and intermediaries Mark Nottingham
#167: Content-Location on 304 responses Mark Nottingham
Re: [draft-nottingham-http-link-header-06] rev Mark Nottingham
#169: private and no-cache CC directives w/ header args Mark Nottingham
Re: [draft-nottingham-http-link-header-06] rev Ian Hickson
Re: [draft-nottingham-http-link-header-06] rev Mark Nottingham
Re: Link: grandfathered format-specific registered relations Mark Nottingham

Saturday, 22 August 2009

Re: Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Roy T. Fielding
Re: Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Julian Reschke
Re: Link: grandfathered format-specific registered relations Roy T. Fielding
Re: Link: grandfathered format-specific registered relations Mark Nottingham
Re: Link: grandfathered format-specific registered relations Roy T. Fielding
Re: Link: grandfathered format-specific registered relations Mark Nottingham
Re: Link: grandfathered format-specific registered relations Nicolas Alvarez

Friday, 21 August 2009

Re: Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Roy T. Fielding
Re: [draft-nottingham-http-link-header-06] rev Julian Reschke
Re: [draft-nottingham-http-link-header-06] rev Sam Johnston
Re: [draft-nottingham-http-link-header-06] rev Mark Nottingham
Re: [draft-nottingham-http-link-header-06] rev Julian Reschke
Hiroshima Mark Nottingham
Re: [draft-nottingham-http-link-header-06] 4.1 Registered Relation Types Mark Nottingham
Re: [draft-nottingham-http-link-header-06] relation-types Mark Nottingham
Re: Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Julian Reschke
Re: [draft-nottingham-http-link-header-06] rev Mark Nottingham
Re: Link: grandfathered format-specific registered relations Mark Nottingham
Re: anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham

Thursday, 20 August 2009

Re: Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Roy T. Fielding
Re: link header rev parameters, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: link header rev parameters, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: link header rev parameters, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson
Re: link header rev parameters Anne van Kesteren
Re: link header rev parameters, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: link header rev parameters, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
link header rev parameters, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Fixing the IANA HTTP upgrade token registry, Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Sam Johnston
Re: Link: grandfathered format-specific registered relations Sam Johnston
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Link: grandfathered format-specific registered relations Mark Nottingham
RE: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Eran Hammer-Lahav
Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Mark Nottingham

Wednesday, 19 August 2009

Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham

Monday, 17 August 2009

Re: [httpbis] #81: Content Negotiation for media types Mark Nottingham

Sunday, 16 August 2009

Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Julian Reschke
Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Henrik Nordstrom

Saturday, 15 August 2009

Re: #172 (take over HTTP Upgrade Token Registry) – httpbis Julian Reschke

Thursday, 13 August 2009

Re: #184: HTTP/0.9 Henrik Nordstrom
Re: #184: HTTP/0.9 Julian Reschke

Wednesday, 12 August 2009

Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Anne van Kesteren
Re: #173: CR and LF in chunk extension values Mark Nottingham

Tuesday, 11 August 2009

Re: #184: HTTP/0.9 Jamie Lokier
Re: #184: HTTP/0.9 David Morris
Re: #184: HTTP/0.9 Julian Reschke
Re: #184: HTTP/0.9 Roy T. Fielding
Re: #184: HTTP/0.9 Geoffrey Sneddon
Re: #184: HTTP/0.9 Dan Winship
Re: #184: HTTP/0.9 Julian Reschke
Re: #184: HTTP/0.9 William A. Rowe, Jr.

Monday, 10 August 2009

Re: #173: CR and LF in chunk extension values Henrik Nordstrom
Re: #184: HTTP/0.9 Henrik Nordstrom
Re: #184: HTTP/0.9 Julian Reschke
Re: #184: HTTP/0.9 Dan Winship
Re: #184: HTTP/0.9 Julian Reschke
Re: #184: HTTP/0.9 Julian Reschke
Re: #184: HTTP/0.9 David Morris
#173: CR and LF in chunk extension values Mark Nottingham
#184: HTTP/0.9 Mark Nottingham
Re: Issue 131 (increase connection limit), Re: p1-message-07 S 7.1.4 Mark Nottingham
Re: Update on issue 155 (Content Sniffing) Mark Nottingham
Re: Issue 187 (Warn header (P6) vs RFC2047 encoding) Mark Nottingham

Saturday, 8 August 2009

draft-abarth-cookie-00 Adam Barth

Friday, 7 August 2009

Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) Julian Reschke
Issue 188, was: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) Julian Reschke
Re: iPhone streaming Internet-Draft posted Jamie Lokier
Re: Issue 187 (Warn header (P6) vs RFC2047 encoding) Julian Reschke

Thursday, 6 August 2009

Re: iPhone streaming Internet-Draft posted Roger Pantos
Re: iPhone streaming Internet-Draft posted Roy T. Fielding
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Update on issue 155 (Content Sniffing) Julian Reschke
Re: Issue 131 (increase connection limit), Re: p1-message-07 S 7.1.4 Daniel Stenberg
Re: Issue 131 (increase connection limit), Re: p1-message-07 S 7.1.4 David Morris
Re: Issue 131 (increase connection limit), Re: p1-message-07 S 7.1.4 Adrien de Croy
Re: Issue 131 (increase connection limit), Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: Review of new HTTPbis text for 303 See Other Ian Davis

Wednesday, 5 August 2009

Re: #110: how to determine what entity a response carries Mark Nottingham
#81: content negotiation for type Mark Nottingham
Re: Issue 187 (Warn header (P6) vs RFC2047 encoding) Julian Reschke
Re: Update on issue 155 (Content Sniffing) Anne van Kesteren
Re: Issue 131 (increase connection limit), Re: p1-message-07 S 7.1.4 Mark Nottingham
Re: Issue 187 (Warn header (P6) vs RFC2047 encoding) Mark Nottingham
Re: Update on issue 155 (Content Sniffing) Mark Nottingham
Re: Issue 187 (Warn header (P6) vs RFC2047 encoding) Yves Lafon
Re: iPhone streaming Internet-Draft posted David Singer
Re: Issue 187 (Warn header (P6) vs RFC2047 encoding) Henrik Nordstrom
Re: iPhone streaming Internet-Draft posted Mark Nottingham
Re: Update on issue 155 (Content Sniffing) Roy T. Fielding
Issue 187 (Warn header (P6) vs RFC2047 encoding) Julian Reschke
Re: Update on issue 155 (Content Sniffing) Anne van Kesteren

Tuesday, 4 August 2009

Re: iPhone streaming Internet-Draft posted Roy T. Fielding
Re: iPhone streaming Internet-Draft posted Mark Nottingham
Re: iPhone streaming Internet-Draft posted David Singer
Re: iPhone streaming Internet-Draft posted David Singer
Re: iPhone streaming Internet-Draft posted David Singer
Re: Update on issue 155 (Content Sniffing) Mark Nottingham
Re: Minutes uploaded Roy T. Fielding
Re: Minutes uploaded Julian Reschke
Re: Minutes uploaded Adam Barth
Minutes uploaded Mark Nottingham
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: draft-reschke-rfc2231-in-http-02 Daniel Stenberg
Re: draft-reschke-rfc2231-in-http-02 Julian Reschke
Re: "Document", "Resource", "Representation", recommended reading Alan Ruttenberg
Re: "Document", "Resource", "Representation", recommended reading Alan Ruttenberg

Monday, 3 August 2009

Re: iPhone streaming Internet-Draft posted Mark Nottingham
RE: [OAUTH-WG] [oauth] #4: Error Codes Eran Hammer-Lahav
RE: [OAUTH-WG] [oauth] #4: Error Codes Eran Hammer-Lahav
New SIP HTTP Subscription Package Mailing List Adam Roach
"Document", "Resource", "Representation", recommended reading Larry Masinter
Re: iPhone streaming Internet-Draft posted Daniel Stenberg

Sunday, 2 August 2009

Re: iPhone streaming Internet-Draft posted David Singer
Re: iPhone streaming Internet-Draft posted Daniel Stenberg
Re: Review of new HTTPbis text for 303 See Other Tim Berners-Lee
Re: iPhone streaming Internet-Draft posted Roger Pantos
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Ian Hickson
anchor parameter, was: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke

Saturday, 1 August 2009

Re: The demise of the Netscape Doc??? (cookie_spec.html) Jamie Lokier

Friday, 31 July 2009

draft-reschke-rfc2231-in-http-02 Daniel Stenberg
Re: Fwd: Review of new HTTPbis text for 303 See Other Julian Reschke
Re: Fwd: Review of new HTTPbis text for 303 See Other noah_mendelsohn@us.ibm.com
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Fwd: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: The demise of the Netscape Doc??? (cookie_spec.html) Bil Corry
Multi-server HTTP Ford, Alan
New issue: p5-range 5.4.2, proxy recommendations regarding 200 responses to Range Henrik Nordstrom
HTTP-state WG being resurrected? =JeffH
re: The demise of the Netscape Doc??? (cookie_spec.html) =JeffH
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Henrik Nordstrom
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Daniel Stenberg
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Adrien de Croy
Re: Issue #73: definition of deflate encoding David Morris

Thursday, 30 July 2009

Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Henrik Nordstrom
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Adrien de Croy
Re: comments on draft-barth-mime-sniffing Ian Hickson
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Anthony Bryan
Re: Update on issue 155 (Content Sniffing) Adam Barth
Re: Update on issue 155 (Content Sniffing) Henrik Nordstrom
Re: Update on issue 155 (Content Sniffing) Anne van Kesteren
Update on issue 155 (Content Sniffing) Julian Reschke
Re: issue 79: must understand content-* header fields or fail Sam Johnston
issue 79: must understand content-* header fields or fail Roy T. Fielding
Re: Issue 43 (combining fragments) Julian Reschke
Re: Issue #73: definition of deflate encoding Henrik Nordstrom
Re: Issue #73: definition of deflate encoding Mark Nottingham
HTTPbis Working Group Meeting Julian Reschke
Re: iPhone streaming Internet-Draft posted Mark Nottingham
Re: Issue #73: definition of deflate encoding David Morris

Wednesday, 29 July 2009

Re: iPhone streaming Internet-Draft posted David Singer
Re: fyi: Tab-level cookies for the browser Bil Corry
Re: fyi: Tab-level cookies for the browser David Morris
Re: fyi: Tab-level cookies for the browser Yngve N. Pettersen
Re: fyi: Tab-level cookies for the browser Bil Corry
Re: fyi: Tab-level cookies for the browser Yngve N. Pettersen
Re: fyi: Tab-level cookies for the browser David Morris
Re: Proposal: Is OPTIONS Safe? [#171] Henrik Nordstrom
Re: Proposal: Is OPTIONS Safe? [#171] Mark Nottingham
RE: [httpbis] #81: Content Negotiation for media types Larry Masinter
Re: Issue 43 (combining fragments) Yngve N. Pettersen
Issue #73: definition of deflate encoding Henrik Nordstrom
Re: fyi: Tab-level cookies for the browser =JeffH
Re: fyi: Tab-level cookies for the browser Daniel Stenberg
fyi: Tab-level cookies for the browser =JeffH
Re: On the use of weak ETags for authoring Julian Reschke

Tuesday, 28 July 2009

Re: Content-MD5 and partial responses Henrik Nordstrom
Re: Issue 43 (combining fragments) Henrik Nordstrom
Re: Issue 43 (combining fragments) Julian Reschke
Re: Issue 43 (combining fragments) Henrik Nordstrom
Re: Issue 43 (combining fragments) Henrik Nordstrom
Re: Proposed fix for issued 140: 301 Julian Reschke
Issue 43 (combining fragments) Julian Reschke
Re: Content-MD5 and partial responses Yves Lafon
Re: Issue 152: range unit in Range header for custom ranges, was: issue 85 - range unit extensions Yves Lafon
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors David Morris

Monday, 27 July 2009

Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Daniel Stenberg
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Sam Johnston
Re: HTTP Extensions for Simultaneous Download from Multiple Mirrors Henrik Nordstrom
RE: [Ltru] Issue 181, was: Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: Proposed resolution for Issue 13 (language tags) Phillips, Addison
Re: [Ltru] Issue 181, was: Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: Proposed resolution for Issue 13 (language tags) John Cowan
Re: Semantics of extension methods Henrik Nordstrom
Re: Last Call: draft-nottingham-http-link-header (from digest) Phillips, Addison
RE: Issue 181, was: Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: [Ltru] Proposed resolution for Issue 13 (language tags) Phillips, Addison
Re: Semantics of extension methods Julian Reschke
Re: Proposal: Is OPTIONS Safe? [#171] Julian Reschke
Re: Semantics of extension methods Henrik Nordstrom
Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) Bjoern Hoehrmann
draft-sharhalakis-httptz-05 Stefanos Harhalakis
Semantics of extension methods Julian Reschke
Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) Julian Reschke
Re: [draft-nottingham-http-link-header-06] anchor link-param? Julian Reschke
Re: Ticket 162, was: Ambiguity in ABNF for comment Julian Reschke
Re: Content-MD5 and partial responses Jamie Lokier
Issue 181, was: Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: [Ltru] Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: Content-MD5 and partial responses Yves Lafon
Re: Content-MD5 and partial responses Henrik Nordstrom
Re: Content-MD5 and partial responses Yves Lafon

Sunday, 26 July 2009

Re: [draft-nottingham-http-link-header-06] extension tokens Anne van Kesteren
Re: [draft-nottingham-http-link-header-06] extension tokens Julian Reschke
Re: [draft-nottingham-http-link-header-06] extension tokens Anne van Kesteren
Re: Content-MD5 and partial responses Jamie Lokier
Re: Content-MD5 and partial responses Henrik Nordstrom
Re: Content-MD5 and partial responses Roy T.Fielding

Saturday, 25 July 2009

Re: Questions (errata?) about caching authenticated responses [#174] Henrik Nordstrom
Re: Content-MD5 and partial responses Henrik Nordstrom
Re: Content-MD5 and partial responses Yves Lafon
Re: Questions (errata?) about caching authenticated responses [#174] Mark Nottingham
Re: clients ignoring brokenness of sites Jamie Lokier

Friday, 24 July 2009

Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Daniel Stenberg
Re: p1-message-07 S 7.1.4 Jamie Lokier
Re: Questions (errata?) about caching authenticated responses [#174] Henrik Nordstrom
Re: [draft-nottingham-http-link-header-06] anchor link-param? Julian Reschke
Re: [draft-nottingham-http-link-header-06] HTML4 profile Julian Reschke
Re: Content-MD5 and partial responses Henrik Nordstrom
Re: Content-Disposition handling ? Julian Reschke
Re: Content-Disposition handling ? Julian Reschke
Re: [draft-nottingham-http-link-header-06] extension tokens Julian Reschke
Re: Content-Disposition handling ? 신정식, 申政湜
Content-Disposition handling ? 신정식, 申政湜
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
RE: BCP 47 reference (was Re: Last Call: draft-nottingham-http-link-header from digest) Phillips, Addison
Re: BCP 47 reference (was Re: Last Call: draft-nottingham-http-link-header from digest) Noah Slater
Re: p1-message-07 S 7.1.4 Jamie Lokier
BCP 47 reference (was Re: Last Call: draft-nottingham-http-link-header from digest) Phillips, Addison
[draft-nottingham-http-link-header-06] extension tokens Anne van Kesteren
Re: Content-MD5 and partial responses Jamie Lokier
[draft-nottingham-http-link-header-06] HTML4 profile Anne van Kesteren
[draft-nottingham-http-link-header-06] anchor link-param? Anne van Kesteren
[draft-nottingham-http-link-header-06] relation-types Anne van Kesteren
[draft-nottingham-http-link-header-06] rev Anne van Kesteren
[draft-nottingham-http-link-header-06] 4.1 Registered Relation Types Anne van Kesteren
Re: Content-MD5 and partial responses Yves Lafon
Re: Content-MD5 and partial responses Adrien de Croy
Re: Content-MD5 and partial responses Mark Nottingham
Re: Content-MD5 and partial responses Henrik Nordstrom
Re: Content-MD5 and partial responses Yves Lafon
Re: p6 2.7 combining 206 & ETag, p5 5.3 If-Range Yves Lafon
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Warn header (P6) vs RFC2047 encoding Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: p6 2.7, suggested resolutions to comments 10 & 11. Henrik Nordstrom
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: p6 2.7 combining 206 & ETag, p5 5.3 If-Range Mark Nottingham
Re: p6 2.7, suggested resolutions to comments 10 & 11. Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Questions (errata?) about caching authenticated responses [#174] Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: requested resource / entity / representation / variant again.. Henrik Nordstrom
Re: requested resource / entity / representation / variant again.. Henrik Nordstrom
Re: requested resource / entity / representation / variant again.. Henrik Nordstrom
p6 2.7 combining 206 & ETag, p5 5.3 If-Range Henrik Nordstrom
Re: requested resource / entity / representation / variant again.. Mark Nottingham
Re: requested resource / entity / representation / variant again.. Mark Nottingham
p6 2.7, suggested resolutions to comments 10 & 11. Henrik Nordstrom

Thursday, 23 July 2009

RE: p1-message-07 S 7.1.4 Larry Masinter
Re: requested resource / entity / representation / variant again.. Henrik Nordstrom
Re: requested resource / entity / representation / variant again.. Henrik Nordstrom
Re: requested resource / entity / representation / variant again.. Mark Nottingham
Re: requested resource / entity / representation / variant again.. Mark Nottingham
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: Warn header (P6) vs RFC2047 encoding Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: Warn header (P6) vs RFC2047 encoding Julian Reschke
Re: clients ignoring brokenness of sites Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Adrien de Croy
Re: Warn header (P6) vs RFC2047 encoding Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: Content-MD5 and partial responses Henrik Nordstrom
Warn header (P6) vs RFC2047 encoding Julian Reschke
Re: requested resource / entity / representation / variant again.. Henrik Nordstrom
Re: "up" relation, was: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Ian Hickson
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: "up" relation, was: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: clients ignoring brokenness of sites Adam Barth
Re: p1-message-07 S 7.1.4 Adrien de Croy
Re: clients ignoring brokenness of sites Adrien de Croy
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Re: clients ignoring brokenness of sites Adrian Chadd
clients ignoring brokenness of sites Adrien de Croy
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: requested resource / entity / representation / variant again.. Mark Nottingham

Wednesday, 22 July 2009

Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Anne van Kesteren
Re: Comments on draft-ietf-httpbis-p2-semantics-07 Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Patrick McManus
Re: Comments on draft-ietf-httpbis-p2-semantics-07 Hugh Winkler

Tuesday, 21 July 2009

Re: requested resource / entity / representation / variant again.. Adrien de Croy
Re: p1-message-07 S 7.1.4 Adrien de Croy
Re: (issue 30) - concrete security-related examples Henrik Nordstrom
Re: (issue 30) - concrete security-related examples William A. Rowe, Jr.
Re: (issue 30) - concrete security-related examples William A. Rowe, Jr.
requested resource / entity / representation / variant again.. Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: Review of new HTTPbis text for 303 See Other Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Jamie Lokier
Re: p1-message-07 S 7.1.4 Jamie Lokier
Re: Proposed fix for issued 140 Julian Reschke
Re: (issue 30) - concrete security-related examples Amit Klein
[OFF-TOPIC WARNING] Review of new HTTPbis text for 303 See Other Mark Nottingham
Re: Review of new HTTPbis text for 303 See Other Dan Brickley
Re: (issue 30) - concrete security-related examples Mark Nottingham
Re: Review of new HTTPbis text for 303 See Other Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Mark Nottingham

Monday, 20 July 2009

Re: 100 Continue and Expects Adrien de Croy
Re: 100 Continue and Expects Adrien de Croy
Re: 100 Continue and Expects Daniel Stenberg
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Lowry Improved_Living~
Re: p1-message-07 S 7.1.4 Adrien de Croy
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Issue 160 (Redirects and non-GET methods), was: Proposed fix for issued 140: 301 Julian Reschke
Re: p1-message-07 S 7.1.4 Adrien de Croy
Re: Issue 161, was: Base for first-byte-pos, last-byte-pos, suffix-length Julian Reschke
Re: p1-message-07 S 7.1.4 Mark Nottingham
Re: p1-message-07 S 7.1.4 Adrien de Croy
Issue 131 (increase connection limit), Re: p1-message-07 S 7.1.4 Julian Reschke
Re: "up" relation, was: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: Comments on draft-ietf-httpbis-p2-semantics-07 Mark Nottingham
Re: #179: Relax Via MUST Mark Nottingham
Re: p1-message-07 S 7.1.4 Mark Nottingham
RE: Proposed fix for issued 140: 301 Manger, James H

Sunday, 19 July 2009

Re: Proposed fix for issued 140 Henrik Nordstrom
Re: p1-message-07 S 7.1.4 Adrien de Croy
Re: "up" relation, was: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Re: "up" relation, was: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: "up" relation, was: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Noah Slater
Proposed IETF/W3C task force: "Resource meaning" Review of new HTTPbis text for 303 See Other Larry Masinter
Re: p1-message-07 S 7.1.4 Henrik Nordstrom
Re: [Ltru] Proposed resolution for Issue 13 (language tags) Julian Reschke
Issue 181 (Accept-Language: which RFC4647 filtering?") Julian Reschke
"up" relation, was: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: 100 Continue and Expects Henrik Nordstrom

Saturday, 18 July 2009

Comments on draft-ietf-httpbis-p2-semantics-07 Hugh Winkler
Re: 100 Continue and Expects Adrien de Croy
Re: 100 Continue and Expects Henrik Nordstrom
Re: Review of new HTTPbis text for 303 See Other Henrik Nordstrom
Re: [Ltru] Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: Proposed resolution for Issue 13 (language tags) Julian Reschke
RE: Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: [Ltru] Proposed resolution for Issue 13 (language tags) Phillips, Addison
RE: [Ltru] Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: Proposed resolution for Issue 13 (language tags) Phillips, Addison
Re: [Ltru] Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: [Ltru] Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: Proposed resolution for Issue 13 (language tags) John Cowan
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: [Ltru] Proposed resolution for Issue 13 (language tags) Julian Reschke
RE: [Ltru] Proposed resolution for Issue 13 (language tags) Phillips, Addison
Proposed fix for issued 140 Julian Reschke
Re: Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: Connection limits (issue 131), was: p1-message-07 S 7.1.4 Adrien de Croy
Connection limits (issue 131), was: p1-message-07 S 7.1.4 Julian Reschke
Re: Host header vs host in absolute-URI Henrik Nordstrom
100 Continue and Expects Adrien de Croy
p1-message-07 S 7.1.4 Adrien de Croy
Re: Host header vs host in absolute-URI Adrien de Croy
Re: comments on draft-barth-mime-sniffing Boris Zbarsky
Fwd: DataCache API - editor's draft available Mark Nottingham

Friday, 17 July 2009

Re: comments on draft-barth-mime-sniffing Ian Hickson
Re: Host header vs host in absolute-URI Henrik Nordstrom
RE: DanC's Web Addresses draft (was: Comments on the HTTP Sec-From Header (draft-abarth-origin)) Larry Masinter
Re: On the use of weak ETags for authoring Julian Reschke
Host header vs host in absolute-URI Adrien de Croy
Re: #179: Relax Via MUST Henrik Nordstrom
Re: #179: Relax Via MUST Adrien de Croy
Re: #179: Relax Via MUST Adrien de Croy
Re: #179: Relax Via MUST Henrik Nordstrom
Re: #179: Relax Via MUST Henrik Nordstrom
Re: #179: Relax Via MUST Jamie Lokier
Re: #179: Relax Via MUST Adrien de Croy
Re: #179: Relax Via MUST Henrik Nordstrom
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Henrik Nordstrom
Re: #179: Relax Via MUST Mark Nottingham
Re: #179: Relax Via MUST Adrien de Croy
Re: #179: Relax Via MUST Mark Nottingham
Re: #179: Relax Via MUST Adrien de Croy
Re: #179: Relax Via MUST Mark Nottingham
Re: #179: Relax Via MUST Adrien de Croy
Re: #179: Relax Via MUST Roy T. Fielding
Re: [#177] Realm required on challenges Henrik Nordstrom
Re: On the use of weak ETags for authoring Henrik Nordstrom
Re: [#177] Realm required on challenges Henrik Nordstrom
Re: Review of new HTTPbis text for 303 See Other Henrik Nordstrom
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Henrik Nordstrom
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: #179: Relax Via MUST Mark Nottingham

Thursday, 16 July 2009

Re: #179: Relax Via MUST Henrik Nordstrom
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Nicolás Alvarez
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Review of new HTTPbis text for 303 See Other David Booth
Re: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Julian Reschke
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Phil Archer
Fwd: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard Mark Nottingham
Re: iPhone streaming Internet-Draft posted Mark Nottingham
Re: Review of new HTTPbis text for 303 See Other Mark Nottingham

Wednesday, 15 July 2009

Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other David Morris
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Review of new HTTPbis text for 303 See Other Manfred Baedke
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other David Booth
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Ray Denenberg, Library of Congress
On the use of weak ETags for authoring Julian Reschke
Re: Review of new HTTPbis text for 303 See Other Julian Reschke
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Mark Nottingham
httpbis p[1-7]-07 published Mark Nottingham
Preliminary agenda for Stockholm Mark Nottingham
Re: "privacy-sensitive" context (was: Comments on the HTTP Sec-From Header (draft-abarth-origin)) Bil Corry
Re: "privacy-sensitive" context (was: Comments on the HTTP Sec-From Header (draft-abarth-origin)) =JeffH
Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Review of new HTTPbis text for 303 See Other Richard Cyganiak

Tuesday, 14 July 2009

Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) =JeffH
re: URI or IRI (was: Comments on the HTTP Sec-From Header (draft-abarth-origin)) =JeffH
RE: Review of new HTTPbis text for 303 See Other Nick Gall
RE: Review of new HTTPbis text for 303 See Other Larry Masinter
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) J Ross Nicoll
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Jim Gettys
[Fwd: Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00)] J Ross Nicoll
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Jim Gettys
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) J Ross Nicoll
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Carsten Bormann
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Jim Gettys
Re: Link Relations and languages Noah Slater
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Adrian Chadd
Re: Link Relations and languages Sam Johnston
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Daniel Stenberg
Re: Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Julian Reschke
Chopan - Compressed HTTP Over PANs (draft-frank-6lowpan-chopan-00) Julian Reschke
Re: Review of new HTTPbis text for 303 See Other Alan Ruttenberg
Re: Review of new HTTPbis text for 303 See Other Richard Cyganiak

Monday, 13 July 2009

Re: DanC's Web Addresses draft (was: Comments on the HTTP Sec-From Header (draft-abarth-origin)) Dan Connolly
Re: DanC's Web Addresses draft (was: Comments on the HTTP Sec-From Header (draft-abarth-origin)) Ian Hickson
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) =JeffH
Re: DanC's Web Addresses draft (was: Comments on the HTTP Sec-From Header (draft-abarth-origin)) =JeffH
Link Relations and languages Noah Slater
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Richard Cyganiak
Re: Review of new HTTPbis text for 303 See Other Richard Cyganiak
I-D Action:draft-ietf-httpbis-p6-cache-07.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p7-auth-07.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p5-range-07.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p3-payload-07.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p2-semantics-07.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p1-messaging-07.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p4-conditional-07.txt Internet-Drafts@ietf.org
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Julian Reschke
#179: Relax Via MUST Mark Nottingham
[#54] 13.1.2's Definition of 1xx Warn-Codes Mark Nottingham
Re: The HTTP Origin Header (draft-abarth-origin) Adam Barth
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Re: The HTTP Origin Header (draft-abarth-origin) Bil Corry
Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham

Sunday, 12 July 2009

Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Fwd: New Version Notification for draft-nottingham-http-link-header-06 Mark Nottingham
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham

Saturday, 11 July 2009

Re: Review of new HTTPbis text for 303 See Other Alan Ruttenberg
Re: Review of new HTTPbis text for 303 See Other Alan Ruttenberg
Re: Review of new HTTPbis text for 303 See Other Alan Ruttenberg
Re: Review of new HTTPbis text for 303 See Other Chimezie Ogbuji
Re: Review of new HTTPbis text for 303 See Other Richard Cyganiak

Thursday, 9 July 2009

Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Roy T. Fielding
Re: Review of new HTTPbis text for 303 See Other Roy T. Fielding
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
FW: New Version Notification for draft-natarajan-http-over-sctp-02 Preethi Natarajan (prenatar)
Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Roy T. Fielding
Re: Review of new HTTPbis text for 303 See Other Xiaoshu Wang
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other J Ross Nicoll
Re: Review of new HTTPbis text for 303 See Other Julian Reschke
Re: Review of new HTTPbis text for 303 See Other Jonathan Rees
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Ian Hickson
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Julian Reschke
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Ian Hickson
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Julian Reschke
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Ian Hickson
Re: Comments on the HTTP Sec-From Header (draft-abarth-origin) Adam Barth
Comments on the HTTP Sec-From Header (draft-abarth-origin) Mark Nottingham

Wednesday, 8 July 2009

Re: Review of new HTTPbis text for 303 See Other David Morris
Re: Review of new HTTPbis text for 303 See Other Roy T. Fielding
Re: Review of new HTTPbis text for 303 See Other Jonathan Rees
Re: Review of new HTTPbis text for 303 See Other Roy T. Fielding
Re: Review of new HTTPbis text for 303 See Other David Booth
Re: Review of new HTTPbis text for 303 See Other Pat Hayes
Re: Review of new HTTPbis text for 303 See Other Jonathan Rees
Re: Review of new HTTPbis text for 303 See Other Julian Reschke
Re: Review of new HTTPbis text for 303 See Other Roy T. Fielding
Re: Review of new HTTPbis text for 303 See Other Julian Reschke
Re: Review of new HTTPbis text for 303 See Other Yves Lafon

Tuesday, 7 July 2009

Re: [#177] Realm required on challenges Jeff Jenkins
Re: [#177] Realm required on challenges Adrien de Croy
Re: Review of new HTTPbis text for 303 See Other ashok malhotra
Re: Review of new HTTPbis text for 303 See Other Jonathan Rees
Re: NULL paths in requests Henrik Nordstrom
Re: [#177] Realm required on challenges Jeff Jenkins
Re: [#177] Realm required on challenges Jim Luther
Re: [#177] Realm required on challenges Thomas Broyer
Re: [#177] Realm required on challenges Robert Collins
Re: [#177] Realm required on challenges Thomas Broyer
Re: [#177] Realm required on challenges Adrien de Croy
Re: [#177] Realm required on challenges Thomas Broyer
Re: [#177] Realm required on challenges Robert Collins
Re: [#177] Realm required on challenges Alexey Melnikov
Re: [#177] Realm required on challenges Adrien de Croy
Re: [#177] Realm required on challenges Mark Nottingham
[#177] Realm required on challenges Mark Nottingham
Re: httpbis-p6-cache-06 and no-store response directive David Morris

Monday, 6 July 2009

Re: Requests that do now allow bodies (do they exist?), was: Proposal: 205 Bodies [#88] Julian Reschke
Re: Editorship of p6-caching Julian Reschke

Sunday, 5 July 2009

Re: NULL paths in requests Roy T. Fielding
Fwd: I-D Action:draft-pettersen-cookie-v2-04.txt Yngve N. Pettersen (Developer Opera Software ASA)
Fwd: I-D Action:draft-pettersen-cache-context-04.txt Yngve N. Pettersen (Developer Opera Software ASA)
Re: NULL paths in requests Adrien de Croy

Saturday, 4 July 2009

Re: NULL paths in requests Roy T. Fielding
NULL paths in requests Adrien de Croy

Friday, 3 July 2009

Re: draft-nottingham-http-link-header-05: a question and an experimental implementation Phil Archer
Re: draft-nottingham-http-link-header-05: a question and an experimental implementation Michael Burrows
Re: Content-MD5 and partial responses Yves Lafon
Re: httpbis-p6-cache-06 and no-store response directive Henrik Nordstrom
Editorship of p6-caching Mark Nottingham

Thursday, 2 July 2009

Re: draft-nottingham-http-link-header-05: a question and an experimental implementation Mark Nottingham

Wednesday, 1 July 2009

Re: Review of new HTTPbis text for 303 See Other Julian Reschke
Re: Content-MD5 and partial responses Adrian Chadd
Re: comments on draft-barth-mime-sniffing Boris Zbarsky

Last message date: Wednesday, 30 September 2009 11:21:32 UTC