ietf-http-wg@w3.org from April to June 2008 by date

Saturday, 28 June 2008

Re: The "unsafe" charset Henrik Nordstrom
Re: The "unsafe" charset Julian Reschke
The "unsafe" charset Robert Brewer

Thursday, 26 June 2008

Re: Issue 72 Frank Ellermann
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Julian Reschke
RE: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Larry Masinter
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Julian Reschke

Wednesday, 25 June 2008

Re: Content-Disposition (new issue?) Julian Reschke

Friday, 20 June 2008

Re: Content-Disposition (new issue?) Julian Reschke
RE: Content-Disposition (new issue?) Brian Smith
Re: Content-Disposition (new issue?) Julian Reschke
Re: Content-Disposition (new issue?) Julian Reschke
RE: Content-Disposition (new issue?) Brian Smith
Issue 121 (RFC 1806 vs RFC2183), was: Content-Disposition (new issue?) Julian Reschke
Re: Content-Disposition (new issue?) Julian Reschke
Re: Content-Disposition (new issue?) Julian Reschke
Re: Content-Disposition (new issue?) Frank Ellermann
Re: Content-Disposition (new issue?) Julian Reschke
Re: relation registry Frank Ellermann
Re: Content-Disposition (new issue?) Frank Ellermann
Re: relation registry Julian Reschke
Re: relation registry Frank Ellermann
Content-Disposition (new issue?) Julian Reschke
Re: relation registry Julian Reschke

Thursday, 19 June 2008

relation registry (was: bug in default base URI in "HTTP Header Linking"?) Frank Ellermann
Re: bug in default base URI in "HTTP Header Linking"? Julian Reschke
bug in default base URI in "HTTP Header Linking"? Dan Connolly

Tuesday, 17 June 2008

New drafts published Julian Reschke
I-D Action:draft-ietf-httpbis-p3-payload-03.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p2-semantics-03.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p5-range-03.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p7-auth-03.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p6-cache-03.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p4-conditional-03.txt Internet-Drafts@ietf.org
I-D Action:draft-ietf-httpbis-p1-messaging-03.txt Internet-Drafts@ietf.org
Re: Basic auth and realms Adrien de Croy
Re: Basic auth and realms Bjoern Hoehrmann

Monday, 16 June 2008

Re: Basic auth and realms Adrien de Croy
Re: NEW ISSUE: repeating non-list-type-headers Julian Reschke

Sunday, 15 June 2008

Re: Basic auth and realms Bjoern Hoehrmann
Basic auth and realms Adrien de Croy

Saturday, 14 June 2008

Re: planning publication of -03 drafts Julian Reschke

Friday, 13 June 2008

planning publication of -03 drafts Julian Reschke

Thursday, 12 June 2008

Dublin meeting timeslot Mark Nottingham
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Julian Reschke
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Mark Nottingham
Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Julian Reschke
Re: i59 Julian Reschke

Wednesday, 11 June 2008

Re: [DNSOP] Public Suffix List Eric Brunner-Williams
Re: [DNSOP] Public Suffix List Florian Weimer
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: Public Suffix List - Please move discussion to dnsop Mark Nottingham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Henrik Nordstrom
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: Public Suffix List Stephane Bortzmeyer
Re: Public Suffix List Stephane Bortzmeyer
Re: Public Suffix List Stephane Bortzmeyer
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham

Tuesday, 10 June 2008

Re: Public Suffix List Stephane Bortzmeyer
Re: [DNSOP] Public Suffix List Henrik Nordstrom
Re: [DNSOP] Public Suffix List Henrik Nordstrom
Re: [DNSOP] Public Suffix List Henrik Nordstrom
Re: [DNSOP] Public Suffix List Henrik Nordstrom
Re: [DNSOP] Public Suffix List Florian Weimer
Re: [DNSOP] Public Suffix List Florian Weimer
Re: [DNSOP] Public Suffix List Florian Weimer
Re: [DNSOP] Public Suffix List Florian Weimer
Re: [DNSOP] Public Suffix List Florian Weimer
Re: [DNSOP] Public Suffix List Paul Hoffman
Re: i59 Frank Ellermann
Re: i59 Julian Reschke
Re: NEW ISSUE: 13.1.2's Definition of 1xx Warn-Codes Mark Nottingham
Re: i59 Julian Reschke
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: [DNSOP] Public Suffix List Adrien de Croy
Re: [DNSOP] Public Suffix List Henrik Nordstrom
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: Public Suffix List Stephane Bortzmeyer

Monday, 9 June 2008

Re: [DNSOP] Public Suffix List Paul Hoffman
Re: Public Suffix List Adrien de Croy
Re: Public Suffix List Frank Ellermann
Re: [DNSOP] Public Suffix List Eric Brunner-Williams
Re: Public Suffix List Stephane Bortzmeyer
Re: i59 Frank Ellermann
Re: Public Suffix List Stephane Bortzmeyer
Re: Public Suffix List Stephane Bortzmeyer
Re: i59 Lisa Dusseault
Re: Public Suffix List Stephane Bortzmeyer
Re: Public Suffix List Stephane Bortzmeyer
Re: i59 Frank Ellermann
Re: [DNSOP] Public Suffix List Paul Hoffman
Re: [DNSOP] Public Suffix List Eric Brunner-Williams
Re: i59 Julian Reschke
Re: i59 Frank Ellermann
Re: [DNSOP] Public Suffix List Eric Brunner-Williams
Re: [DNSOP] Public Suffix List Patrik Fältström
Re: [DNSOP] Public Suffix List Patrik Fältström
Re: [DNSOP] Public Suffix List bert hubert
RE: [DNSOP] Public Suffix List Antoin Verschuren
Re: [DNSOP] Public Suffix List Elmar K. Bins
Re: [DNSOP] Public Suffix List bert hubert
RE: [DNSOP] Public Suffix List Antoin Verschuren
Re: [DNSOP] Public Suffix List Jeroen Massar
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: [DNSOP] Public Suffix List Gervase Markham
i59, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Julian Reschke
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Jamie Lokier
Re: [DNSOP] Public Suffix List Gervase Markham
Re: Public Suffix List Gervase Markham
Re: Public Suffix List Adrien de Croy
Re: Public Suffix List Frank Ellermann
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Yngve Nysaeter Pettersen
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Yngve Nysaeter Pettersen
Re: Public Suffix List Gervase Markham
Re: [DNSOP] Public Suffix List Gervase Markham
Issue 40, Re: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Julian Reschke
Re: Public Suffix List Frank Ellermann
Re: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Mark Nottingham
Re: [DNSOP] Public Suffix List Gervase Markham
Public Suffix List Gervase Markham

Sunday, 8 June 2008

Re: Implied LWS questions Henrik Nordstrom

Friday, 6 June 2008

Re: Implied LWS questions Frank Ellermann
Re: Implied LWS questions Julian Reschke
Re: Implied LWS questions Geoffrey Sneddon
Re: Implied LWS questions Dan Winship
Re: Implied LWS questions Julian Reschke
Re: Implied LWS questions Frank Ellermann
Implied LWS questions Julian Reschke
Re: Content Disposition Julian Reschke

Thursday, 5 June 2008

Re: Content Disposition J Ross Nicoll
Re: Basic Authentication J Ross Nicoll
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Yves Lafon
Re: i28 proposed replacement text Adrien de Croy
Re: i28 proposed replacement text Robert Siemer
Re: i28 proposed replacement text Yves Lafon

Wednesday, 4 June 2008

Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: Content-Disposition Julian Reschke
Re: Content-Disposition Frank Ellermann
Re: Content-Disposition Julian Reschke
Content-Disposition (was: Status of IANA Considerations (registrations and registries) -- issues 40, [...]) Frank Ellermann

Tuesday, 3 June 2008

Re: i28 proposed replacement text Robert Siemer
Re: i28 proposed replacement text Julian Reschke
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Julian Reschke
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Julian Reschke
Re: i28 proposed replacement text Yves Lafon
Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 Julian Reschke
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Yves Lafon

Monday, 2 June 2008

RE: 100-continue implementation status question Henrik Nordstrom
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: Resolve issue 98? Henrik Nordstrom
Re: Basic Authentication and encoding of non-ASCII characters in credentials Henrik Nordstrom
Re: i28 proposed replacement text Jamie Lokier
Re: Struggling with LWS (2616) vs LWSP (2831bis) Henrik Nordstrom
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Henrik Nordstrom
Re: Resolve issue 98? Julian Reschke
Re: i28 proposed replacement text Yves Lafon
Re: Resolve issue 98? Mark Nottingham
Re: 100-continue implementation status question Mark Nottingham

Sunday, 1 June 2008

Re: 100-continue implementation status question Julian Reschke

Friday, 30 May 2008

RE: combining ranges Brian Smith
Re: draft-nottingham-http-link-header-01.txt - problem with default relationship base URI Jonathan Rees
Re: draft-nottingham-http-link-header-01.txt - problem with default relationship base URI Julian Reschke
Re: draft-nottingham-http-link-header-01.txt - problem with default relationship base URI Julian Reschke
draft-nottingham-http-link-header-01.txt - problem with default relationship base URI Jonathan Rees
Re: Proposal: i67 - quoting charsets Julian Reschke
Resolve issue 98? Julian Reschke

Thursday, 29 May 2008

Re: Proposal: i67 - quoting charsets Julian Reschke
RE: Proposal: i67 - quoting charsets Brian Smith
Re: Proposal: i67 - quoting charsets Julian Reschke

Wednesday, 28 May 2008

Re: i28 proposed replacement text Henrik Nordstrom
Re: 401 Unauthenticated, 403 Unauthorized? Werner Baumann
Re: Proposal: i67 - quoting charsets Julian Reschke
RE: Proposal: i67 - quoting charsets Brian Smith
Re: Proposal: i67 - quoting charsets Julian Reschke
Re: i28 proposed replacement text Yves Lafon

Thursday, 22 May 2008

401 Unauthenticated, 403 Unauthorized? Miles Crawford

Saturday, 24 May 2008

ranges and chunked encoding Doug Moore
combining ranges Doug Moore

Wednesday, 28 May 2008

Re: Basic Authentication and encoding of non-ASCII characters in credentials Frank Ellermann
Re: Basic Authentication and encoding of non-ASCII characters in credentials Julian Reschke
Re: Basic Authentication and encoding of non-ASCII characters in credentials Julian Reschke
Re: Basic Authentication and encoding of non-ASCII characters in credentials Martin Duerst

Tuesday, 27 May 2008

Basic Authentication and encoding of non-ASCII characters in credentials Julian Reschke
Re: ABNF switch: list rules Frank Ellermann
Re: Struggling with LWS (2616) vs LWSP (2831bis) Frank Ellermann
Re: ABNF switch: list rules Frank Ellermann
Re: Struggling with LWS (2616) vs LWSP (2831bis) Julian Reschke
Re: Struggling with LWS (2616) vs LWSP (2831bis) Frank Ellermann
Fwd: httpbis - Update to a Meeting Session Request for IETF 72 Mark Nottingham

Monday, 26 May 2008

Struggling with LWS (2616) vs LWSP (2831bis) Julian Reschke
Re: Proposal: i67 - quoting charsets Julian Reschke
HTTPBis Summary Mark Nottingham
i28 - revised proposal Mark Nottingham
Re: #23 Proposal Mark Nottingham
Re: Proposal: i67 - quoting charsets Mark Nottingham

Saturday, 24 May 2008

Re: ABNF switch: list rules Mark Nottingham
Re: ABNF switch: list rules Mark Nottingham
Re: ABNF switch: list rules Frank Ellermann
Re: ABNF switch: list rules Frank Ellermann
Re: i28 proposed replacement text Julian Reschke
Re: i28 proposed replacement text Julian Reschke
Re: ABNF switch: list rules Julian Reschke
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: ABNF switch: list rules Zed A. Shaw
Re: ABNF switch: list rules Julian Reschke
Re: ABNF switch: list rules Julian Reschke
Re: i28 proposed replacement text Julian Reschke
Re: ABNF switch: list rules Zed A. Shaw

Friday, 23 May 2008

Re: ABNF switch: list rules Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Joe Orton
Re: i28 proposed replacement text Henrik Nordstrom
Re: ABNF switch: list rules Julian Reschke
Re: i28 proposed replacement text Mark Nottingham

Thursday, 22 May 2008

Re: ABNF switch: list rules Jamie Lokier
Re: ABNF switch: list rules Bjoern Hoehrmann
Re: ABNF switch: list rules Alexey Melnikov
ABNF switch: list rules Julian Reschke

Tuesday, 20 May 2008

Re: default for q-values in Accept-Language and elsewhere Julian Reschke

Monday, 19 May 2008

Re: default for q-values in Accept-Language and elsewhere Javier Godoy
Re: default for q-values in Accept-Language and elsewhere Julian Reschke

Sunday, 18 May 2008

RE: [#116] ETags and concurrency control Pablo Castro

Friday, 16 May 2008

Re: Likely OT: "closing the connection" Henrik Nordstrom

Thursday, 15 May 2008

Re: Likely OT: "closing the connection" Frank Ellermann
Re: Likely OT: "closing the connection" (was: i28 proposed replacement text) Henrik Nordstrom
Likely OT: "closing the connection" (was: i28 proposed replacement text) Frank Ellermann
#67 (was: HTTPBis Summary) Frank Ellermann
Re: [#116] ETags and concurrency control Julian Reschke

Wednesday, 14 May 2008

Re: [#116] ETags and concurrency control Julian Reschke
Fwd: httpbis - New Meeting Session Request for IETF 72 Mark Nottingham
Re: i28 proposed replacement text Jamie Lokier

Tuesday, 13 May 2008

Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Jamie Lokier
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Jamie Lokier
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Mark Nottingham
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Henrik Nordstrom
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Adrien de Croy
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Jamie Lokier
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Roy T. Fielding
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Jamie Lokier
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Stefan Eissing

Monday, 12 May 2008

Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Adrien de Croy
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Henrik Nordstrom
Isto pode salvar sua vida.... nao deixe de ler.....hdrwqw Dra. Roberta Rosental
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Brian Smith
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Jamie Lokier
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Yves Lafon
Re: i28 proposed replacement text Henrik Nordstrom
Re: i28 proposed replacement text Bjoern Hoehrmann
Re: i28 proposed replacement text Henrik Nordstrom

Sunday, 11 May 2008

Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Henrik Nordstrom
Re: [#116] ETags and concurrency control Henrik Nordstrom
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Mark Nottingham

Saturday, 10 May 2008

Re: i28 proposed replacement text Yves Lafon
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Brian Smith
Re: i109: Clarify entity / representation / variant terminology Brian Smith
Re: i109: Clarify entity / representation / variant terminology Julian Reschke

Friday, 9 May 2008

Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Mark Nottingham
Re: I-D Action:draft-nottingham-http-stale-if-error-01.txt Roy T. Fielding
Fwd: I-D Action:draft-nottingham-http-stale-while-revalidate-01.txt Mark Nottingham
Fwd: I-D Action:draft-nottingham-http-stale-if-error-01.txt Mark Nottingham
Re: i109: Clarify entity / representation / variant terminology Roy T. Fielding
Re: i109: Clarify entity / representation / variant terminology Brian Smith
Re: [#116] ETags and concurrency control Julian Reschke
Re: i109: Clarify entity / representation / variant terminology Julian Reschke
Re: i109: Clarify entity / representation / variant terminology Stefan Eissing
Re: [#116] ETags and concurrency control Julian Reschke
HTTPBis Summary Mark Nottingham
Dublin meeting Mark Nottingham
Re: i28 proposed replacement text Stefan Eissing
i109: Clarify entity / representation / variant terminology Mark Nottingham
Re: #23 Proposal Stefan Eissing
Re: Proposal: i67 - quoting charsets Mark Nottingham
Re: i28 proposed replacement text Mark Nottingham
#23 Proposal Mark Nottingham
Re: Proposal for i23: no-store invalidation Mark Nottingham
[#116] ETags and concurrency control Mark Nottingham
UA control of LM subrange cache-conditional requests Mark Nottingham

Wednesday, 7 May 2008

Re: default for q-values in Accept-Language and elsewhere Martin Duerst

Thursday, 8 May 2008

Re: ETags and concurrency control Mark Nottingham

Wednesday, 7 May 2008

Re: default for q-values in Accept-Language and elsewhere Bjoern Hoehrmann
default for q-values in Accept-Language and elsewhere Javier Godoy
Re: default for q-values in Accept-Language and elsewhere Julian Reschke
Re: default for q-values in Accept-Language and elsewhere Adrien de Croy
default for q-values in Accept-Language and elsewhere Martin Duerst
Re: Problem with q values in Accept-Language Brian Smith
RE: Problem with q values in Accept-Language Roberto Javier Godoy
Re: Problem with q values in Accept-Language Mark Davis
Re: Problem with q values in Accept-Language Brian Smith
Problem with q values in Accept-Language Mark Davis

Tuesday, 6 May 2008

Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Phil Archer
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Julian Reschke
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Phil Archer
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Julian Reschke
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Anne van Kesteren
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Phil Archer
XMLHttpRequest (XHR) in W3C Last Call Julian Reschke

Monday, 5 May 2008

Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Julian Reschke
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Brian Smith
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Julian Reschke
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Julian Reschke

Friday, 2 May 2008

Re: ETags and concurrency control Jamie Lokier
Re: ETags and concurrency control Werner Baumann
Re: ETags and concurrency control Jamie Lokier
Re: ETags and concurrency control Julian Reschke
Re: ETags and concurrency control Henrik Nordstrom
Re: ETags and concurrency control Julian Reschke
Re: ETags and concurrency control Werner Baumann
RE: ETags and concurrency control Henrik Nordstrom
RE: ETags and concurrency control Pablo Castro
Re: ETags and concurrency control Julian Reschke
Re: ETags and concurrency control Mark Baker

Thursday, 1 May 2008

RE: ETags and concurrency control Brian Smith
Re: ETags and concurrency control Adrien de Croy
RE: ETags and concurrency control Brian Smith

Wednesday, 30 April 2008

Re: Content-Location issues (was RE: I-D ACTION:draft-nottingham-http-link-header-01.txt) Henrik Nordstrom
Content-Location issues (was RE: I-D ACTION:draft-nottingham-http-link-header-01.txt) Brian Smith
RE: I-D ACTION:draft-nottingham-http-link-header-01.txt Henrik Nordstrom
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Frank Ellermann

Tuesday, 29 April 2008

RE: I-D ACTION:draft-nottingham-http-link-header-01.txt Brian Smith
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Mark Nottingham
RE: I-D ACTION:draft-nottingham-http-link-header-01.txt Brian Smith
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Phil Archer
RE: I-D ACTION:draft-nottingham-http-link-header-01.txt Brian Smith
RE: I-D ACTION:draft-nottingham-http-link-header-01.txt Brian Smith
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Jamie Lokier
Re: I-D ACTION:draft-nottingham-http-link-header-01.txt Phil Archer

Monday, 28 April 2008

Re: ETags and concurrency control Henrik Nordstrom
Re: ETags and concurrency control Robert Siemer
RE: ETags and concurrency control Brian Smith
RE: I-D ACTION:draft-nottingham-http-link-header-01.txt Brian Smith
RE: I-D ACTION:draft-nottingham-http-link-header-01.txt Brian Smith

Saturday, 26 April 2008

Re: 100-continue implementation status question Tim Olsen

Friday, 25 April 2008

RE: 100-continue implementation status question Paul Leach
Re: 100-continue implementation status question Julian Reschke
100-continue implementation status question Paul Leach

Friday, 18 April 2008

Re: i28 proposed replacement text Yves Lafon

Thursday, 17 April 2008

Re: Proposal for i23: no-store invalidation Henrik Nordstrom
Re: Proposal for i23: no-store invalidation David Morris
Re: Proposal for i111 / i63 Julian Reschke
Re: Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: Proposal for i23: no-store invalidation Henrik Nordstrom
Re: Proposal for i111 / i63 Frank Ellermann
RE: Proposal for i111 / i63 Brian Smith
HTTPBis Summary Mark Nottingham
Re: Proposal for i111 / i63 Mark Nottingham
Re: PROPOSAL: i99 Pipelining Problems Mark Nottingham
Re: Proposal for i23: no-store invalidation Mark Nottingham

Wednesday, 16 April 2008

Re: Proposed resolution for Issue 13 (language tags) Frank Ellermann
Re: Proposed resolution for Issue 13 (language tags) Frank Ellermann
Re: Proposal for i70: cacheability of status 303 Mark Nottingham
RE: [Ltru] Proposed resolution for Issue 13 (language tags) Debbie Garside
RE: [Ltru] Proposed resolution for Issue 13 (language tags) Phillips, Addison
RE: [Ltru] Proposed resolution for Issue 13 (language tags) Phillips, Addison
Re: [Ltru] Proposed resolution for Issue 13 (language tags) Mark Davis
Re: [Ltru] Proposed resolution for Issue 13 (language tags) Mark Davis
RE: [Ltru] Proposed resolution for Issue 13 (language tags) Debbie Garside
Re: [Ltru] Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: [Ltru] Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: Proposed resolution for Issue 13 (language tags) Martin Duerst

Tuesday, 15 April 2008

Re: Proposed resolution for Issue 13 (language tags) Frank Ellermann
RE: [Ltru] Proposed resolution for Issue 13 (language tags) Phillips, Addison
RE: [Ltru] Proposed resolution for Issue 13 (language tags) Phillips, Addison
Re: Proposal for i70: cacheability of status 303 Julian Reschke
Re: Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: Proposed resolution for Issue 13 (language tags) Julian Reschke
Re: Proposed resolution for Issue 13 (language tags) Stephane Bortzmeyer
Re: Proposed resolution for Issue 13 (language tags) Frank Ellermann
Re: Proposed resolution for Issue 13 (language tags) Stephane Bortzmeyer
Re: Proposed resolution for Issue 13 (language tags) Stephane Bortzmeyer
Re: Proposed resolution for Issue 13 (language tags) Frank Ellermann
Re: Proposed resolution for Issue 13 (language tags) Martin Duerst
OT: dream (was: Proposal: i67 - quoting charsets) Frank Ellermann

Monday, 14 April 2008

Re: Proposed resolution for Issue 13 (language tags) David Morris
Re: Proposal: i67 - quoting charsets David Morris
RE: Proposed resolution for Issue 13 (language tags) Brian Smith
Re: Proposed resolution for Issue 13 (language tags) Frank Ellermann
Proposed resolution for Issue 13 (language tags) Julian Reschke

Saturday, 12 April 2008

Fwd: I-D candidate: draft-sharhalakis-httptz-03.txt Stefanos Harhalakis

Friday, 11 April 2008

Re: Proposal for i70: cacheability of status 303 Julian Reschke
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Proposal: i67 - quoting charsets Mark Nottingham
Re: Proposal: i67 - quoting charsets Henrik Nordstrom
Re: Deploying new expectation-extensions Mark Nottingham
Re: Deploying new expectation-extensions Charles Fry

Thursday, 10 April 2008

Re: Deploying new expectation-extensions Alex Rousskov
Re: Deploying new expectation-extensions Mark Nottingham
Re: i67: quoting charsets Julian Reschke
Re: PUT: store "under" vs. "at", was: [ietf-http-wg] <none> Julian Reschke
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Julian Reschke
Re: Proposal: i67 - quoting charsets Frank Ellermann
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Henrik Nordstrom
Re: Proposal: i67 - quoting charsets Julian Reschke
OpenPGP for HTTP Arturo 'Buanzo' Busleiman
Re: Deploying new expectation-extensions Charles Fry
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Julian Reschke

Wednesday, 9 April 2008

Re: PUT: store "under" vs. "at", was: [ietf-http-wg] <none> Mark Nottingham
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Julian Reschke
Re: Updated Proposal: i24 Requiring Allow in 405 Responses John Kemp
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Julian Reschke
Resumption of upload Lisa Dusseault
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Julian Reschke
Re: Updated Proposal: i24 Requiring Allow in 405 Responses David Morris
PUT: store "under" vs. "at", was: [ietf-http-wg] <none> Julian Reschke
Re: i51, was: Moving to editorial: i39 / i51 / i61 / i64 / i94 Julian Reschke
SV: sketch of a simple authentication protocol Per-Olav Gramstad
Re: sketch of a simple authentication protocol Story Henry
Re: sketch of a simple authentication protocol Story Henry
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Adrien de Croy
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Adrien de Croy
Re: Updated Proposal: i24 Requiring Allow in 405 Responses John Kemp

Tuesday, 8 April 2008

Re: Upload negotiation Adrien de Croy
[ietf-http-wg] <none> Robert Brewer
Re: Upload negotiation Henrik Nordstrom
Re: Upload negotiation Adrien de Croy
Re: Upload negotiation Patrick McManus
Re: Upload negotiation Henrik Nordstrom
Re: Upload negotiation Henrik Nordstrom
Re: Upload negotiation Henrik Nordstrom
Re: Upload negotiation Henrik Nordstrom
Re: Upload negotiation Adrien de Croy
Re: Upload negotiation Adrien de Croy
Re: Upload negotiation Adrien de Croy
Re: [google-gears-eng] Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Proposal: i67 - quoting charsets Henrik Nordstrom
Re: Upload negotiation Adrien de Croy
Re: Proposal for i23: no-store invalidation Henrik Nordstrom
Re: Upload negotiation Henrik Nordstrom
Re: Upload negotiation Adrien de Croy
Re: Upload negotiation Henrik Nordstrom
Re: [google-gears-eng] Re: Deploying new expectation-extensions Adrien de Croy
Re: HTTPBis Summary Mark Nottingham
Re: i51, was: Moving to editorial: i39 / i51 / i61 / i64 / i94 Mark Nottingham
Proposal: i67 - quoting charsets Mark Nottingham
Re: PROPOSAL: i99 Pipelining Problems Mark Nottingham
Re: Proposal for i23: no-store invalidation Mark Nottingham
Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham

Monday, 7 April 2008

Re: [google-gears-eng] Re: Deploying new expectation-extensions Henrik Nordstrom
Re: [google-gears-eng] Re: Deploying new expectation-extensions Adrien de Croy
Re: Deploying new expectation-extensions Jamie Lokier
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Implicit *LWS Geoffrey Sneddon
Re: [google-gears-eng] Re: Deploying new expectation-extensions Jamie Lokier
RE: PROPOSAL: i74: Encoding for non-ASCII headers Brian Smith
Re: [google-gears-eng] Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Implicit *LWS Henrik Nordstrom
Re: [google-gears-eng] Re: Deploying new expectation-extensions Jamie Lokier
Re: PROPOSAL: i99 Pipelining Problems Henrik Nordstrom
Implicit *LWS Geoffrey Sneddon
Re: PROPOSAL: i99 Pipelining Problems Jamie Lokier
Re: [google-gears-eng] Re: Deploying new expectation-extensions Adrien de Croy
Re: PROPOSAL: i99 Pipelining Problems Henrik Nordstrom
Re: PROPOSAL: i99 Pipelining Problems Mark Nottingham
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Mark Nottingham
Re: [google-gears-eng] Re: Deploying new expectation-extensions Charles Fry

Sunday, 6 April 2008

Re: PROPOSAL: i99 Pipelining Problems Henrik Nordstrom
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Henrik Nordstrom
Re: PROPOSAL: i99 Pipelining Problems David Morris
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: PROPOSAL: i99 Pipelining Problems Henrik Nordstrom
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Deploying new expectation-extensions Jamie Lokier
Re: PROPOSAL: i99 Pipelining Problems Jamie Lokier
Re: Deploying new expectation-extensions Jamie Lokier
Re: Updated Proposal: i24 Requiring Allow in 405 Responses Julian Reschke
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: [google-gears-eng] Re: Deploying new expectation-extensions Adrien de Croy
Re: Deploying new expectation-extensions Adrien de Croy
Re: Deploying new expectation-extensions Mark Nottingham
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Deploying new expectation-extensions Mark Nottingham
Re: PROPOSAL: i99 Pipelining Problems Henrik Nordstrom

Saturday, 5 April 2008

Re: i67: quoting charsets Henrik Nordstrom
Re: [google-gears-eng] Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Deploying new expectation-extensions Nicolas Alvarez
Re: [google-gears-eng] Re: Deploying new expectation-extensions Henrik Nordstrom
Re: [google-gears-eng] Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: PROPOSAL: i74: Encoding for non-ASCII headers Henrik Nordstrom
Re: Deploying new expectation-extensions Henrik Nordstrom
Re: sketch of a simple authentication protocol Henrik Nordstrom
Re: Proposal for i23: no-store invalidation Henrik Nordstrom
Re: [google-gears-eng] Re: Deploying new expectation-extensions Charles Fry
Re: [google-gears-eng] Re: Deploying new expectation-extensions Charles Fry
Re: Deploying new expectation-extensions Charles Fry
Re: Deploying new expectation-extensions Bill de hOra
Re: PROPOSAL: i99 Pipelining Problems Julian Reschke
Re: [google-gears-eng] Re: Deploying new expectation-extensions Julian Reschke
Re: [google-gears-eng] Re: Deploying new expectation-extensions Adrien de Croy
Re: Deploying new expectation-extensions Roy T. Fielding
Re: [google-gears-eng] Re: Deploying new expectation-extensions Charles Fry

Friday, 4 April 2008

Re: [google-gears-eng] Re: Deploying new expectation-extensions Adrien de Croy
Re: PROPOSAL: i99 Pipelining Problems Roy T. Fielding
Re: [google-gears-eng] Re: Deploying new expectation-extensions Julian Reschke
Re: [google-gears-eng] Re: Deploying new expectation-extensions Brian McBarron
Re: PROPOSAL: i99 Pipelining Problems Julian Reschke
Re: i67: quoting charsets Martin Duerst
Re: Deploying new expectation-extensions Jamie Lokier
Re: HTTPBis Summary Mark Nottingham
i67: quoting charsets Mark Nottingham
Re: Deploying new expectation-extensions Adrien de Croy
HTTPBis Summary Mark Nottingham
Re: Deploying new expectation-extensions Roy T. Fielding
Re: Deploying new expectation-extensions Mark Baker
Re: Deploying new expectation-extensions Adrien de Croy
Re: Deploying new expectation-extensions Charles Fry
Re: Deploying new expectation-extensions Charles Fry
Re: i39, was: Moving to editorial: i39 / i51 / i61 / i64 / i94 Mark Nottingham
Re: i94, was: Does Reason-Phrase allow LWS? Mark Nottingham
Proposal for i111 / i63 Mark Nottingham
Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham
Re: PROPOSAL: i74: Encoding for non-ASCII headers Roy T. Fielding
Re: i94, was: Does Reason-Phrase allow LWS? Mark Nottingham
Re: Deploying new expectation-extensions Jamie Lokier
Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham
Re: Deploying new expectation-extensions Mark Nottingham
Re: Deploying new expectation-extensions Charles Fry
Re: Deploying new expectation-extensions Mark Nottingham
Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham

Thursday, 3 April 2008

Re: Deploying new expectation-extensions Charles Fry
Re: PROPOSAL: i74: Encoding for non-ASCII headers Roy T. Fielding
Re: Deploying new expectation-extensions Mark Nottingham
Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham
Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier
Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham
Re: PROPOSAL: i74: Encoding for non-ASCII headers Julian Reschke
Re: PROPOSAL: i74: Encoding for non-ASCII headers Jamie Lokier
Re: i94, was: Does Reason-Phrase allow LWS? Frank Ellermann
Deploying new expectation-extensions Julian Reschke
Re: PROPOSAL: i74: Encoding for non-ASCII headers Julian Reschke
Re: i94, was: Does Reason-Phrase allow LWS? Julian Reschke
Re: i94, was: Does Reason-Phrase allow LWS? Frank Ellermann
i39, was: Moving to editorial: i39 / i51 / i61 / i64 / i94 Julian Reschke
i51, was: Moving to editorial: i39 / i51 / i61 / i64 / i94 Julian Reschke
i94, was: Does Reason-Phrase allow LWS? Julian Reschke
Re: Moving to editorial: i39 / i51 / i61 / i64 / i94 Julian Reschke
Re: Moving to editorial: i39 / i51 / i61 / i64 / i94 Julian Reschke
Re: Proposal for i70: cacheability of status 303 Julian Reschke
RE: NEW ISSUE: cacheability of status 303 Julian Reschke
Re: sketch of a simple authentication protocol Story Henry
Re: sketch of a simple authentication protocol Toby A Inkster
Updated Proposal: i24 Requiring Allow in 405 Responses Mark Nottingham
Re: i28 proposed replacement text Mark Nottingham
Proposal for i70: cacheability of status 303 Mark Nottingham
Closing i41: Security Considerations Mark Nottingham
Proposal for i23: no-store invalidation Mark Nottingham
Re: Moving to editorial: i39 / i51 / i61 / i64 / i94 Frank Ellermann
Moving to editorial: i39 / i51 / i61 / i64 / i94 Mark Nottingham

Wednesday, 2 April 2008

Re: PROPOSAL: i24 Requiring Allow in 405 Responses Henrik Nordstrom
Re: Sketch of a very simple identification protocol Arturo 'Buanzo' Busleiman
Re: sketch of a simple authentication protocol Pipian
Re: sketch of a simple authentication protocol Chris Richard
Re: Sketch of a very simple identification protocol Arturo 'Buanzo' Busleiman
Re: Sketch of a very simple identification protocol Arturo 'Buanzo' Busleiman
Re: sketch of a simple authentication protocol Story Henry
Re: PROPOSAL: i24 Requiring Allow in 405 Responses Julian Reschke
Re: Sketch of a very simple identification protocol Story Henry
Re: Sketch of a very simple identification protocol Story Henry
Re: Sketch of a very simple identification protocol Story Henry
Re: PROPOSAL: i74: Encoding for non-ASCII headers Mark Nottingham
Re: PROPOSAL: i76 Use Proxy Henrik Nordstrom
Re: PROPOSAL: i76 Use Proxy Adrien de Croy

Tuesday, 1 April 2008

RE: PROPOSAL: i76 Use Proxy Josh Cohen (MIG)
Re: Sketch of a very simple identification protocol Henrik Nordstrom
Re: Sketch of a very simple identification protocol Lisa Dusseault
Re: PROPOSAL: i76 Use Proxy Henrik Nordstrom
Sketch of a very simple identification protocol Story Henry
Re: PROPOSAL: i76 Use Proxy Julian Reschke
Re: PROPOSAL: i74: Encoding for non-ASCII headers Henrik Nordstrom
Re: PROPOSAL: i74: Encoding for non-ASCII headers Martin Duerst
Re: PROPOSAL: i74: Encoding for non-ASCII headers Martin Duerst
Re: PROPOSAL: i74: Encoding for non-ASCII headers Martin Duerst

Last message date: Saturday, 28 June 2008 23:20:01 UTC