ietf-http-wg@w3.org from January to March 2013 by date

Sunday, 31 March 2013

Re: WGLC: p5 editorial nits Julian Reschke
Re: p6: Returning the freshest response Amos Jeffries

Saturday, 30 March 2013

WGLC: p4 304 (Not Modified) Ken Murchison

Friday, 29 March 2013

Re: p6: Returning the freshest response Martin Thomson
Re: p6: Returning the freshest response Mark Nottingham
Re: p6: Returning the freshest response Mark Nottingham
Re: Choosing a header compression algorithm James M Snell
Re: Choosing a header compression algorithm Roberto Peon
Re: p6: Returning the freshest response Martin Thomson
Re: p6: Returning the freshest response Ken Murchison
Re: p6: Returning the freshest response Martin Thomson
Re: p6: Returning the freshest response Martin Thomson
RE: Header compression: header set diff RUELLAN Herve
RE: Choosing a header compression algorithm RUELLAN Herve
Re: p6: Returning the freshest response Ken Murchison
Re: p6: Returning the freshest response Eitan Adler
p6: Returning the freshest response Mark Nottingham

Thursday, 28 March 2013

WGLC: p5 editorial nits Ken Murchison
Re: Choosing a header compression algorithm Roberto Peon
Re: Choosing a header compression algorithm Roberto Peon
draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion Dave Thaler
RE: Choosing a header compression algorithm RUELLAN Herve
RE: Choosing a header compression algorithm RUELLAN Herve
Re: Choosing a header compression algorithm Roberto Peon
Re: Choosing a header compression algorithm James M Snell
Re: Choosing a header compression algorithm Roberto Peon
Re: Choosing a header compression algorithm Roberto Peon

Wednesday, 27 March 2013

Re: REFUSED_STREAM and CANCEL Amos Jeffries

Tuesday, 26 March 2013

WGLC: p4 editorial nits Ken Murchison
Re: INVALID_STREAM and STREAM_ALREADY_CLOSED 陈智昌
Re: REFUSED_STREAM and CANCEL Martin Thomson
Re: REFUSED_STREAM and CANCEL Martin Thomson
Re: INVALID_STREAM and STREAM_ALREADY_CLOSED Martin Thomson
Re: REFUSED_STREAM and CANCEL Roberto Peon
Re: REFUSED_STREAM and CANCEL Martin Thomson
Re: REFUSED_STREAM and CANCEL Roberto Peon
Re: INVALID_STREAM and STREAM_ALREADY_CLOSED 陈智昌
Re: REFUSED_STREAM and CANCEL 陈智昌
Re: REFUSED_STREAM and CANCEL Roberto Peon
Re: INVALID_STREAM and STREAM_ALREADY_CLOSED Roberto Peon
INVALID_STREAM and STREAM_ALREADY_CLOSED Martin Thomson
REFUSED_STREAM and CANCEL Martin Thomson
Re: Choosing a header compression algorithm Roberto Peon
RE: HeaderDiff specification RUELLAN Herve
答复: HeaderDiff specification wrong string
RE: Choosing a header compression algorithm RUELLAN Herve
Re: Choosing a header compression algorithm Roberto Peon

Monday, 25 March 2013

WGLC: p6 editorial nits Ken Murchison
Re: Project idea Roberto Peon
Re: Choosing a header compression algorithm Roberto Peon
Re: Header compression: header set diff James M Snell
RE: Header compression: header set diff RUELLAN Herve
RE: Choosing a header compression algorithm RUELLAN Herve
Re: Project idea Gábor Molnár
Re: DNS record support and draft-lear-httpbis-svcinfo-rr Eliot Lear
Re: DNS record support and draft-lear-httpbis-svcinfo-rr Patrick McManus
Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" Julian Reschke
Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" Martin J. Dürst
DNS record support and draft-lear-httpbis-svcinfo-rr Eliot Lear
Re: Choosing a header compression algorithm Mark Nottingham
Re: Choosing a header compression algorithm Mark Nottingham

Saturday, 23 March 2013

Re: Choosing a header compression algorithm Roberto Peon

Friday, 22 March 2013

Re: Header compression: header set diff James M Snell
Re: Choosing a header compression algorithm Martin Thomson
Updated delta-encoding of values RUELLAN Herve
RE: Choosing a header compression algorithm RUELLAN Herve
Re: Choosing a header compression algorithm Roberto Peon
RE: Header compression: buffer management RUELLAN Herve
RE: Header compression: buffer management RUELLAN Herve
RE: Header compression: header set diff RUELLAN Herve
RE: Header compression: header set diff RUELLAN Herve
RE: Choosing a header compression algorithm RUELLAN Herve
Re: Header compression: buffer management Poul-Henning Kamp
Re: Header compression: buffer management Poul-Henning Kamp
Re: Choosing a header compression algorithm Roberto Peon
Re: Choosing a header compression algorithm Mark Nottingham

Thursday, 21 March 2013

Re: WGLC p6 4.2.1 Adrien W. de Croy
Re: Header compression: header set diff James M Snell
Re: Header compression: header set diff Roberto Peon
Re: Choosing a header compression algorithm Roberto Peon
Re: Header compression: buffer management Roberto Peon
Re: Header compression: header set diff Roberto Peon
Re: Header compression: header set diff James M Snell
Re: Choosing a header compression algorithm James M Snell
Re: Header compression: buffer management James M Snell
Re: Header compression: buffer management Poul-Henning Kamp
Re: Choosing a header compression algorithm Stephen Farrell
Re: Header compression: buffer management Amos Jeffries
Re: WGLC issue: token68 in p7 Ken Murchison
Re: WGLC issue: token68 in p7 Amos Jeffries
Re: Header compression: header set diff Patrick McManus
Header compression: buffer management RUELLAN Herve
Header compression: header set diff RUELLAN Herve
Re: WGLC issue: token68 in p7 Ken Murchison
RE: Choosing a header compression algorithm RUELLAN Herve
Re: Working Group Last Call on the HTTPbis document set Julian Reschke
Re: WGLC issue: token68 in p7 Julian Reschke
Re: WGLC issue: token68 in p7 Manger, James H
Re: WGLC issue: token68 in p7 Julian Reschke
Choosing a header compression algorithm Mark Nottingham
RE: Dealing with bad server chunking Osama Mazahir

Wednesday, 20 March 2013

Re: WGLC p6 4.2.1 Mark Nottingham
RE: WGLC issue: token68 in p7 Manger, James H
Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" Bjoern Hoehrmann
Re: WGLC issue: token68 in p7 Bjoern Hoehrmann
Delta I-D update feedback James M Snell

Tuesday, 19 March 2013

WGLC: p1 editorial nits Ken Murchison
Re: Host header with an empty value? Zhong Yu
Re: WGLC p6 4.2.1 Roy T. Fielding
Re: Host header with an empty value? Roy T. Fielding
Re: WGLC: p7 editorial nits Julian Reschke
Re: WGLC issue: token68 in p7 Ken Murchison
WGLC: p7 editorial nits Ken Murchison
Re: WGLC issue: token68 in p7 Julian Reschke
WGLC issue: token68 in p7 Ken Murchison

Monday, 18 March 2013

Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" Mark Nottingham
Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" Julian Reschke
Re: draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" Mark Nottingham
draft-ietf-httpbis-p7-auth-22, "2.2 Protection Space (Realm)" Julian Reschke
Re: Comments on draft-ietf-httpbis-p4-conditional-22 Julian Reschke
Re: Comments on draft-ietf-httpbis-p7-auth-22 Julian Reschke
Re: Comments on draft-ietf-httpbis-authscheme-registrations-06 Julian Reschke
Comments on draft-ietf-httpbis-p4-conditional-22 Bjoern Hoehrmann
Comments on draft-ietf-httpbis-p5-range-22 Bjoern Hoehrmann
Comments on draft-ietf-httpbis-p6-cache-22 Bjoern Hoehrmann
Comments on draft-ietf-httpbis-p7-auth-22 Bjoern Hoehrmann
Re: WGLC p6 4.2.1 Fabian Keil
Comments on draft-ietf-httpbis-method-registrations-11 Bjoern Hoehrmann
Comments on draft-ietf-httpbis-authscheme-registrations-06 Bjoern Hoehrmann
Re: WGLC p6 4.2.1 Poul-Henning Kamp
Re: WGLC p6 4.2.1 Adrien W. de Croy
Re: WGLC p6 4.2.1 Poul-Henning Kamp
Re: WGLC p6 4.2.1 Adrien W. de Croy
Re: WGLC p6 4.2.1 Poul-Henning Kamp
HeaderDiff draft RUELLAN Herve
Re: WGLC p6 4.2.1 Adrien W. de Croy
Re: WGLC p6 4.2.1 Amos Jeffries
Re: WGLC p6 4.2.1 Poul-Henning Kamp
Planning for Future Meetings Mark Nottingham

Sunday, 17 March 2013

WGLC p6 4.2.1 Adrien W. de Croy
Re: Dealing with bad server chunking Adrien W. de Croy
Working Group Last Call on the HTTPbis document set Mark Nottingham
Minutes from Orlando Mark Nottingham
Re: delta compression I-D 01 Willy Tarreau
Re: delta compression I-D 01 Fred Akalin

Saturday, 16 March 2013

Re: Host header with an empty value? Willy Tarreau
Re: Host header with an empty value? Zhong Yu
Re: Host header with an empty value? Willy Tarreau
Host header with an empty value? Zhong Yu

Friday, 15 March 2013

Re: delta compression I-D 01 Fred Akalin
RE: Dealing with bad server chunking Osama Mazahir
ALPN OpenSSL implementation Brian Raymor (MS OPEN TECH)
Cisco Research looking for proposals to analyze HTTP 2.0 Eliot Lear
Re: Dealing with bad server chunking Bjoern Hoehrmann
Re: Dealing with bad server chunking Willy Tarreau
Re: Dealing with bad server chunking Julian Reschke
Re: Dealing with bad server chunking Daniel Stenberg
Reminder: WG meeting today Julian Reschke
Re: Dealing with bad server chunking David Morris
Re: Dealing with bad server chunking Willy Tarreau
Dealing with bad server chunking Adrien W. de Croy

Thursday, 14 March 2013

Re: Project idea Ilya Grigorik
Re: iwebpp.io announce - run peer/p2p web service with Node.js tom
Re: Project idea Mark Nottingham
Re: iwebpp.io announce - run peer/p2p web service with Node.js Mark Nottingham
Re: iwebpp.io announce - run peer/p2p web service with Node.js tom
Project idea Gábor Molnár

Wednesday, 13 March 2013

Re: Proposed text for "Routing Data's relationship to headers" (Issue 23) Poul-Henning Kamp
Re: iwebpp.io announce - run peer/p2p web service with Node.js Mark Nottingham
Re: delta compression I-D 01 James M Snell
Re: delta compression I-D 01 Roberto Peon
Re: delta compression I-D 01 James M Snell
delta compression I-D 01 Roberto Peon
Proposed text for "Routing Data's relationship to headers" (Issue 23) Alexey Melnikov
iwebpp.io announce - run peer/p2p web service with Node.js tom
Re: [HTTP/1.1] method length and 501 Not Implemented Amos Jeffries

Tuesday, 12 March 2013

Re: [HTTP/1.1] method length and 501 Not Implemented Bjoern Hoehrmann
Re: [HTTP/1.1] method length and 501 Not Implemented Adrien W. de Croy
Re: [HTTP/1.1] method length and 501 Not Implemented Karl Dubost
Re: [HTTP/1.1] method length and 501 Not Implemented Bjoern Hoehrmann
[HTTP/1.1] method length and 501 Not Implemented Karl Dubost
Fwd: New Version Notification for draft-snell-httpbis-mget-00.txt James M Snell
Re: "In the wild" use case for Accept-Charset with parameters; musings on a modern alternative Karl Dubost
"In the wild" use case for Accept-Charset with parameters; musings on a modern alternative Nicholas Shanks

Monday, 11 March 2013

RE: Maximum Frame Size Thomas Maslen
Re: Maximum Frame Size James M Snell
Re: Maximum Frame Size Martin Thomson
RE: Maximum Frame Size Thomas Maslen
Re: Giving the Framing Layer a real name Karl Dubost
Talking to yourself Martin Thomson
Complete Request Flow Martin Thomson

Friday, 8 March 2013

Re: The document's address Martin Thomson
Re: The document's address Eitan Adler
Re: The document's address Albert Lunde
Re: The document's address Julian Reschke
Re: The document's address Nicholas Shanks
Re: The document's address Julian Reschke
Re: The document's address Nicholas Shanks

Thursday, 7 March 2013

Re: Preference-Applied Response Header Julian Reschke
Re: Preference-Applied Response Header Ken Murchison
Re: Preference-Applied Response Header Julian Reschke
Preference-Applied Response Header Ken Murchison
Re: Intercepting proxies - yet again Nicolas mailhot
Re: Giving the Framing Layer a real name Willy Tarreau
Re: Giving the Framing Layer a real name Yoav Nir
Intercepting proxies - yet again Adrien W. de Croy
Re: Giving the Framing Layer a real name David Kendal

Wednesday, 6 March 2013

Re: #40 - HTTP2 default value for client supported max_concurrent_streams 陈智昌
RE: #40 - HTTP2 default value for client supported max_concurrent_streams DRUTA, DAN
Re: draft-ietf-httpbis-http2-01, "4.2.3 Authentication" Nicolas Mailhot
Re: draft-ietf-httpbis-http2-01, "4.2.3 Authentication" Julian Reschke
Re: draft-ietf-httpbis-http2-01, "4.2.3 Authentication" Nicolas Mailhot

Tuesday, 5 March 2013

draft-ietf-httpbis-http2-01, "4.2.3 Authentication" Julian Reschke
Re: Maximum Frame Size Martin Thomson
Re: Maximum Frame Size Patrick McManus

Monday, 4 March 2013

Maximum Frame Size Martin Thomson
Re: Multi-GET, extreme compression? Phillip Hallam-Baker
Re: Multi-GET, extreme compression? Julian Reschke
Re: HTTP/2 Header Encoding Status Update Poul-Henning Kamp
Re: HTTP/2 Header Encoding Status Update Eliot Lear
Re: HTTP/2 Header Encoding Status Update Poul-Henning Kamp
Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot
Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot

Sunday, 3 March 2013

Re: HTTP/2 Header Encoding Status Update James M Snell
Re: Header field-name token and leading spaces Karl Dubost
Re: Header field-name token and leading spaces Poul-Henning Kamp
Re: Header field-name token and leading spaces Jeff Pinner
Re: Header field-name token and leading spaces Julian Reschke
Header field-name token and leading spaces Karl Dubost
Re: HTTP/2 Header Encoding Status Update Adrien W. de Croy

Saturday, 2 March 2013

Re: HTTP/2 Header Encoding Status Update James Cloos
Re: HTTP/2 Header Encoding Status Update Eliot Lear
Re: HTTP/2 Header Encoding Status Update Yoav Nir
Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot
Re: HTTP/2 Header Encoding Status Update James M Snell
Re: HTTP/2 Header Encoding Status Update Scott Schmit
Re: HTTP/2 Header Encoding Status Update Scott Schmit
Re: HTTP/2 Header Encoding Status Update James M Snell
Re: HTTP/2 Header Encoding Status Update Scott Schmit

Friday, 1 March 2013

Re: HTTP/2 Header Encoding Status Update James M Snell
Re: HTTP/2 Header Encoding Status Update Nicolas Mailhot

Thursday, 28 February 2013

Re: Upgrade status for impl draft 1 Ted Hardie
Re: Upgrade status for impl draft 1 Eliot Lear
Re: Upgrade status for impl draft 1 Ted Hardie
RE: SYN_REPLY RUELLAN Herve
Re: SYN_REPLY Martin Thomson
Re: Upgrade status for impl draft 1 Eliot Lear
Re: HTTP/2 Header Encoding Status Update Julian Reschke
Re: HTTP/2 Header Encoding Status Update Mark Nottingham
Re: HTTP/2 Header Encoding Status Update Julian Reschke
Re: HTTP/2 Header Encoding Status Update Martin J. Dürst
Re: Upgrade status for impl draft 1 Amos Jeffries
Re: Upgrade status for impl draft 1 Eliot Lear
Re: HTTP/2 Header Encoding Status Update Julian Reschke
Re: Upgrade status for impl draft 1 Eliot Lear
Re: Giving the Framing Layer a real name Roberto Peon
Re: HTTP/2 Header Encoding Status Update Amos Jeffries
Re: Upgrade status for impl draft 1 Amos Jeffries
Re: SYN_REPLY Jeff Pinner
Re: Giving the Framing Layer a real name Jeff Pinner
Re: proposed WINDOW_UPDATE text for session flow control windows Martin Thomson
Re: proposed WINDOW_UPDATE text for session flow control windows 陈智昌
Re: proposed WINDOW_UPDATE text for session flow control windows Roberto Peon
Re: #40 - HTTP2 default value for client supported max_concurrent_streams Roberto Peon
Re: SYN_REPLY Amos Jeffries
Re: #40 - HTTP2 default value for client supported max_concurrent_streams Amos Jeffries
Re: HTTP/2 Header Encoding Status Update James Cloos
Re: proposed WINDOW_UPDATE text for session flow control windows Martin Thomson

Wednesday, 27 February 2013

Re: HTTP/2 Header Encoding Status Update James M Snell
Re: Giving the Framing Layer a real name James M Snell
Re: HTTP/2 Header Encoding Status Update Mark Nottingham
Re: HTTP/2 Header Encoding Status Update James M Snell
Re: HTTP/2 Header Encoding Status Update James M Snell
Re: HTTP/2 Header Encoding Status Update Mark Nottingham
Re: Giving the Framing Layer a real name Roberto Peon
Re: Giving the Framing Layer a real name Mark Nottingham
Re: Giving the Framing Layer a real name Martin Thomson
Re: HTTP/2 Header Encoding Status Update Martin Thomson
Re: Giving the Framing Layer a real name Mark Nottingham
Re: HTTP/2 Header Encoding Status Update Julian Reschke
Re: Upgrade status for impl draft 1 Ted Hardie
Re: Upgrade status for impl draft 1 Eliot Lear
Re: Upgrade status for impl draft 1 Ted Hardie
HTTP/2 Header Encoding Status Update James M Snell
Re: SYN_REPLY Hasan Khalil
Re: #40 - HTTP2 default value for client supported max_concurrent_streams 陈智昌
RE: #40 - HTTP2 default value for client supported max_concurrent_streams Gabriel Montenegro
Re: SYN_REPLY 陈智昌
Re: SYN_REPLY Martin Thomson
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Martin Thomson
Re: SYN_REPLY Roberto Peon
Re: Giving the Framing Layer a real name Roberto Peon
Re: Giving the Framing Layer a real name Carsten Bormann
Re: SYN_REPLY Martin Thomson
Re: Giving the Framing Layer a real name Martin Thomson
Re: Giving the Framing Layer a real name James M Snell
Re: Giving the Framing Layer a real name Roberto Peon
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Martin Thomson
Re: Giving the Framing Layer a real name James M Snell
Re: Giving the Framing Layer a real name Martin Thomson
Re: Multi-GET, extreme compression? Nicolas Mailhot
Re: Multi-GET, extreme compression? Julian Reschke
Re: Multi-GET, extreme compression? Julian Reschke
Re: Multi-GET, extreme compression? James M Snell
Re: Multi-GET, extreme compression? Nicolas Mailhot
Re: Multi-GET, extreme compression? Julian Reschke
Re: Multi-GET, extreme compression? Nicolas Mailhot
Re: Giving the Framing Layer a real name Stefan Eissing
Re: Giving the Framing Layer a real name Mark Nottingham
Re: Giving the Framing Layer a real name Mike Belshe
Re: WGLC issue: ambiguity in part 1 example Roy T. Fielding
Re: Giving the Framing Layer a real name Yehia El-khatib
Re: Giving the Framing Layer a real name Yoav Nir
Re: Giving the Framing Layer a real name TZI
Re: Giving the Framing Layer a real name Fred Akalin
Re: Upgrade status for impl draft 1 Eliot Lear
Re: Giving the Framing Layer a real name Amos Jeffries
Re: Giving the Framing Layer a real name Willy Tarreau
Re: Giving the Framing Layer a real name Robert Collins
Re: Upgrade status for impl draft 1 Mark Nottingham
Re: Giving the Framing Layer a real name 陈智昌
Giving the Framing Layer a real name Mark Nottingham
Re: SYN_REPLY Mark Nottingham
Re: SYN_REPLY 陈智昌
Re: SYN_REPLY James M Snell
Re: SYN_REPLY Mark Nottingham
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY 陈智昌
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY 陈智昌
Re: Upgrade status for impl draft 1 陈智昌
Re: SYN_REPLY Amos Jeffries
Re: Can't see error codes in HTML version of http://http2.github.com/http2-spec/#RST_STREAM Mark Nottingham
Can't see error codes in HTML version of http://http2.github.com/http2-spec/#RST_STREAM 陈智昌
Re: WGLC issue: ambiguity in part 1 example Amos Jeffries
Re: #40 - HTTP2 default value for client supported max_concurrent_streams 陈智昌
Re: SYN_REPLY 陈智昌
Re: #38 - HTTP2 min value for server supported max_concurrent_streams 陈智昌
Re: SYN_REPLY Martin Thomson
Re: SYN_REPLY James M Snell
Re: SYN_REPLY Martin Thomson

Tuesday, 26 February 2013

Re: SYN_REPLY Martin Thomson
Re: WGLC issue: ambiguity in part 1 example Roy T. Fielding
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Yoav Nir
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Roberto Peon
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Yoav Nir
Re: #41: Header Block field name length Roberto Peon
RE: #40 - HTTP2 default value for client supported max_concurrent_streams Gabriel Montenegro
Re: #38 - HTTP2 min value for server supported max_concurrent_streams 陈智昌
Re: #38 - HTTP2 min value for server supported max_concurrent_streams 陈智昌
Memento Internet Draft, new version Herbert van de Sompel
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Patrick McManus
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Albert Lunde
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Eliot Lear
RE: #41: Header Block field name length RUELLAN Herve
RE: #38 - HTTP2 min value for server supported max_concurrent_streams Osama Mazahir
Re: SYN_REPLY James M Snell
Re: SYN_REPLY 陈智昌
Re: #43: SYN_REPLY James M Snell
Re: SYN_REPLY 陈智昌
Re: SYN_REPLY Roberto Peon
Re: #43: SYN_REPLY 陈智昌
Re: SYN_REPLY 陈智昌
Re: #41: Header Block field name length Amos Jeffries
Re: Upgrade status for impl draft 1 Willy Tarreau
Re: Upgrade status for impl draft 1 Mark Nottingham
Re: Upgrade status for impl draft 1 Willy Tarreau
Re: proposed WINDOW_UPDATE text for session flow control windows Mark Nottingham
Re: Upgrade status for impl draft 1 Mark Nottingham
#43: SYN_REPLY Mark Nottingham

Monday, 25 February 2013

#41: Header Block field name length Mark Nottingham
Re: Permitted characters for http keys James M Snell
Re: Permitted characters for http keys Mark Nottingham
RE: HeaderDiff specification RUELLAN Herve
Re: Permitted characters for http keys James M Snell
Re: Permitted characters for http keys Mark Nottingham
Re: Permitted characters for http keys Martin J. Dürst
Draft agenda for Orlando Mark Nottingham
Issues addressed in the -22 drafts Mark Nottingham
Re: Using Github for HTTP2 Mark Nottingham

Sunday, 24 February 2013

Re: #40 - HTTP2 default value for client supported max_concurrent_streams 陈智昌
RE: #40 - HTTP2 default value for client supported max_concurrent_streams Gabriel Montenegro
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Mark Nottingham

Saturday, 23 February 2013

Re: Constant priotrity (Was: SYN_REPLY) Patrick McManus
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Patrick McManus
Re: SYN_REPLY Patrick McManus
Re: HTTP/2.0 Magic Scott Schmit
Re: #40 - HTTP2 default value for client supported max_concurrent_streams 陈智昌
I-D Action: draft-ietf-httpbis-authscheme-registrations-06.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-method-registrations-11.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p2-semantics-22.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p1-messaging-22.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p7-auth-22.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p6-cache-22.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p5-range-22.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p4-conditional-22.txt internet-drafts@ietf.org
Re: #40 - HTTP2 default value for client supported max_concurrent_streams Amos Jeffries
Re: Do we kill the "Host:" header in HTTP/2 ? Amos Jeffries
Re: Request Routing Information [was: Do we kill the Amos Jeffries

Friday, 22 February 2013

Re: #38 - HTTP2 min value for server supported max_concurrent_streams 陈智昌
Re: HTTP/2.0 Magic David Morris
RE: #38 - HTTP2 min value for server supported max_concurrent_streams Osama Mazahir
Re: #38 - HTTP2 min value for server supported max_concurrent_streams 陈智昌
Re: Using Github for HTTP2 Mark Nottingham
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Yoav Nir
Re: #40 - HTTP2 default value for client supported max_concurrent_streams 陈智昌
RE: #40 - HTTP2 default value for client supported max_concurrent_streams Gabriel Montenegro
Re: Request Routing Information [was: Do we kill the Nicolas Mailhot
Re: Do we kill the "Host:" header in HTTP/2 ? Nicolas Mailhot
Re: Using Github for HTTP2 陈智昌
Re: HeaderDiff specification Roberto Peon
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Roberto Peon
Re: #40 - HTTP2 default value for client supported max_concurrent_streams Roberto Peon
Re: #40 - HTTP2 default value for client supported max_concurrent_streams Martin Thomson
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Martin Thomson
HTML Form HTTP Extensions Karl Dubost
Re: Upgrade status for impl draft 1 Willy Tarreau
Fwd: New Version Notification for draft-lear-httpbis-svcinfo-rr-01.txt Eliot Lear
Re: Upgrade status for impl draft 1 Eliot Lear
Re: Upgrade status for impl draft 1 Willy Tarreau
Re: Upgrade status for impl draft 1 Eliot Lear
Re: Upgrade status for impl draft 1 Roland Zink
Re: Upgrade status for impl draft 1 Roberto Peon
Re: Upgrade status for impl draft 1 Roberto Peon
Re: Upgrade status for impl draft 1 Willy Tarreau
Re: #40 - HTTP2 default value for client supported max_concurrent_streams Roberto Peon
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Roberto Peon
Re: Upgrade status for impl draft 1 Roberto Peon
Re: Upgrade status for impl draft 1 Roberto Peon
Re: HeaderDiff specification Roberto Peon
Re: Constant priotrity (Was: SYN_REPLY) Roberto Peon
HeaderDiff specification RUELLAN Herve
Re: #38 - HTTP2 min value for server supported max_concurrent_streams Yoav Nir
Constant priotrity (Was: SYN_REPLY) Yoav Nir
PUT, If-Match, 412 - over-constrained? Grzegorz Calkowski
Re: Upgrade status for impl draft 1 Willy Tarreau
Re: Upgrade status for impl draft 1 Willy Tarreau
#40 - HTTP2 default value for client supported max_concurrent_streams Osama Mazahir
#38 - HTTP2 min value for server supported max_concurrent_streams Osama Mazahir
Re: Upgrade status for impl draft 1 Mark Nottingham
Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" Mark Nottingham
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Martin Thomson
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Amos Jeffries
Re: SYN_REPLY Martin Thomson
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Martin Thomson

Thursday, 21 February 2013

Re: Upgrade status for impl draft 1 Martin Thomson
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Martin Thomson
Re: SYN_REPLY Roberto Peon
Re: SYN_REPLY Roberto Peon
Re: Streaming layer in HTTP/2.0 Roberto Peon
SYN_REPLY Martin Thomson
Streaming layer in HTTP/2.0 Martin Thomson
Re: Upgrade status for impl draft 1 Martin Thomson
Re: Upgrade status for impl draft 1 Eliot Lear
Re: Upgrade status for impl draft 1 James M Snell
Re: HTTP/2.0 Magic Martin Nilsson
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Willy Tarreau
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Willy Tarreau
Re: Removing CREDENTIAL Mark Nottingham
Re: HTTP/2.0 Magic Willy Tarreau
Re: HTTP/2.0 Magic Mark Nottingham
Upgrade status for impl draft 1 Mark Nottingham
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Willy Tarreau
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Willy Tarreau
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Amos Jeffries
Re: HTTP/2.0 Magic Willy Tarreau
Re: HTTP/2.0 Magic Mark Nottingham
Re: Removing CREDENTIAL Roberto Peon
Removing CREDENTIAL Brian Raymor (MS OPEN TECH)

Wednesday, 20 February 2013

Re: proposed WINDOW_UPDATE text for session flow control windows Martin Thomson
Re: proposed WINDOW_UPDATE text for session flow control windows Roberto Peon
Re: proposed WINDOW_UPDATE text for session flow control windows Martin Thomson
Re: proposed WINDOW_UPDATE text for session flow control windows Roberto Peon
Re: proposed WINDOW_UPDATE text for session flow control windows Martin Thomson
Interaction of WINDOW_UPDATE and SETTINGS for Flow Control Martin Thomson
Re: proposed WINDOW_UPDATE text for session flow control windows 陈智昌
Re: proposed WINDOW_UPDATE text for session flow control windows Roberto Peon
Re: proposed WINDOW_UPDATE text for session flow control windows Martin Thomson

Tuesday, 19 February 2013

Re: proposed WINDOW_UPDATE text for session flow control windows 陈智昌
Re: proposed WINDOW_UPDATE text for session flow control windows Mark Nottingham
Re: Permitted characters for http keys Martin Thomson
Permitted characters for http keys Roberto Peon
Re: HTTP/2.0 Magic Martin Thomson
#433, was: WGLC issue: ambiguity in part 1 example Julian Reschke
#434: mention in header field considerations that leading/trailing WS is lossy Julian Reschke
Re: Multi-GET, extreme compression? Nico Williams
Re: HTTP/2.0 Magic Willy Tarreau
Re: moving forward on draft-lear-httpbis-svcinfo-rr Eliot Lear
Re: HTTP/2.0 Magic Mark Nottingham
Re: HTTP/2.0 Magic Willy Tarreau
Re: HTTP/2.0 Magic Mark Nottingham
Re: Multi-GET, extreme compression? Mark Nottingham
Re: Multi-GET, extreme compression? Nico Williams
Re: Multi-GET, extreme compression? Mark Nottingham
Re: Multi-GET, extreme compression? Nico Williams
Re: Multi-GET, extreme compression? Nico Williams
Re: Multi-GET, extreme compression? Mark Baker
Re: #430 / #268 - definition of "public" Mark Nottingham
Re: #430 / #268 - definition of "public" Amos Jeffries
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: http/2 prioritization/fairness bug with proxies Nico Williams
Re: Multi-GET, extreme compression? Brian Pane

Monday, 18 February 2013

Re: Multi-GET, extreme compression? Phillip Hallam-Baker
Fwd: New Version Notification for draft-snell-httpbis-bohe-03.txt James M Snell
Re: Multi-GET, extreme compression? Patrick McManus
Re: HTTP/2.0 #19: Clarify that max-streams is per-direction [WAS: Outstanding Action Items] Mark Nottingham
Re: Multi-GET, extreme compression? Willy Tarreau
Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" Mark Nottingham
HTTP/2.0 #19: Clarify that max-streams is per-direction [WAS: Outstanding Action Items] 陈智昌
Re: Multi-GET, extreme compression? 陈智昌
Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" Amos Jeffries
Re: Multi-GET, extreme compression? Phillip Hallam-Baker
Re: Multi-GET, extreme compression? James M Snell
Re: Multi-GET, extreme compression? James M Snell
Re: Multi-GET, extreme compression? Helge Hess
Re: Multi-GET, extreme compression? Mark Nottingham
Re: Outstanding Action Items Mark Nottingham
Re: Multi-GET, extreme compression? Helge Hess
Re: Outstanding Action Items Mark Nottingham
Re: Outstanding Action Items Mark Nottingham
Re: Multi-GET, extreme compression? 陈智昌
Re: Multi-GET, extreme compression? Helge Hess
Re: Multi-GET, extreme compression? 陈智昌
Re: Multi-GET, extreme compression? Helge Hess
Re: Multi-GET, extreme compression? Dr Robert Mattson
Re: Multi-GET, extreme compression? Bjoern Hoehrmann
Re: Multi-GET, extreme compression? James M Snell
Re: Multi-GET, extreme compression? Dr Robert Mattson
Re: WGLC issue: ambiguity in part 1 example Mark Nottingham
Re: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" Mark Nottingham
Re: #430 / #268 - definition of "public" Mark Nottingham
Re: HTTP/1.1 #223: Allowing heuristic caching for new status codes Mark Nottingham

Sunday, 17 February 2013

Re: Multi-GET, extreme compression? Roberto Peon
Re: Multi-GET, extreme compression? James M Snell
Re: A mechanism to encode HTTP version information in DNS Amos Jeffries
Re: A mechanism to encode HTTP version information in DNS Adrien W. de Croy
Re: A mechanism to encode HTTP version information in DNS Phillip Hallam-Baker
Re: A mechanism to encode HTTP version information in DNS Adrien W. de Croy
Re: Multi-GET, extreme compression? Helge Heß
Re: Multi-GET, extreme compression? Cyrus Daboo
Re: A mechanism to encode HTTP version information in DNS Phillip Hallam-Baker
Re: A mechanism to encode HTTP version information in DNS Patrick McManus
Re: A mechanism to encode HTTP version information in DNS Phillip Hallam-Baker
Re: A mechanism to encode HTTP version information in DNS Eliot Lear
WGLC issue: ambiguity in part 1 example Amos Jeffries

Saturday, 16 February 2013

Re: Multi-GET, extreme compression? 陈智昌
Multi-GET, extreme compression? Phillip Hallam-Baker
Re: A mechanism to encode HTTP version information in DNS Phillip Hallam-Baker
Caching 412 responses Ben Niven-Jenkins
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: A mechanism to encode HTTP version information in DNS Adrien W. de Croy
Re: A mechanism to encode HTTP version information in DNS Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Nicholas Shanks
Re: proposed WINDOW_UPDATE text for session flow control windows 陈智昌

Friday, 15 February 2013

Re: proposed WINDOW_UPDATE text for session flow control windows 陈智昌
Re: How to determine server's decoding capability before sending entity? Amos Jeffries
Re: A mechanism to encode HTTP version information in DNS Adrien W. de Croy
How to determine server's decoding capability before sending entity? Yi, EungJun
Re: http/2 prioritization/fairness bug with proxies Amos Jeffries
Re: A mechanism to encode HTTP version information in DNS Amos Jeffries

Thursday, 14 February 2013

Re: http/2 prioritization/fairness bug with proxies Roberto Peon
Re: http/2 prioritization/fairness bug with proxies Nico Williams
A mechanism to encode HTTP version information in DNS Phillip Hallam-Baker
Re: #428 Accept-Language ordering for identical qvalues Eric J. Bowman
Updated BOHE I-D... James M Snell

Wednesday, 13 February 2013

Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Re: http/2 prioritization/fairness bug with proxies Roberto Peon
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: http/2 prioritization/fairness bug with proxies Nico Williams
Re: #428 Accept-Language ordering for identical qvalues Eric J. Bowman
Re: http/2 prioritization/fairness bug with proxies Roberto Peon
Re: http/2 prioritization/fairness bug with proxies Nico Williams
Re: #428 Accept-Language ordering for identical qvalues Martin Thomson
Re: #428 Accept-Language ordering for identical qvalues James M Snell
Re: #428 Accept-Language ordering for identical qvalues Eric J. Bowman
Re: http/2 prioritization/fairness bug with proxies Amos Jeffries
Re: Delta Compression and UTF-8 Header Values Roberto Peon

Tuesday, 12 February 2013

Re: Delta Compression and UTF-8 Header Values James Cloos
Re: HTTP Origin and Hop Hints and Prefer Header Mark Nottingham
Re: http/2 prioritization/fairness bug with proxies Roberto Peon
HTTP Origin and Hop Hints and Prefer Header James M Snell
Re: http/2 prioritization/fairness bug with proxies Nico Williams
Re: proposed WINDOW_UPDATE text for session flow control windows Patrick McManus
Re: HTTP 2.0 next steps and TLS next protocol negotiation Yoav Nir
Re: http/2 prioritization/fairness bug with proxies Yoav Nir
Re: moving forward on draft-lear-httpbis-svcinfo-rr Eliot Lear
Re: HTTP 2.0 next steps and TLS next protocol negotiation Roberto Peon
HTTP 2.0 next steps and TLS next protocol negotiation Brian Raymor (MS OPEN TECH)

Monday, 11 February 2013

Re: http/2 prioritization/fairness bug with proxies Nico Williams
Re: http/2 prioritization/fairness bug with proxies Roberto Peon
Re: http/2 prioritization/fairness bug with proxies Martin Thomson
Re: http/2 prioritization/fairness bug with proxies Roberto Peon
Re: http/2 prioritization/fairness bug with proxies Martin Thomson
Re: moving forward on draft-lear-httpbis-svcinfo-rr Phillip Hallam-Baker
Re: http/2 prioritization/fairness bug with proxies Roberto Peon
Re: Delta Compression and UTF-8 Header Values Roberto Peon
Re: http/2 prioritization/fairness bug with proxies Martin Thomson
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: moving forward on draft-lear-httpbis-svcinfo-rr Martin Thomson
Re: http/2 prioritization/fairness bug with proxies Martin Thomson
Re: Delta Compression and UTF-8 Header Values James Cloos
RE: proposed WINDOW_UPDATE text for session flow control windows Roberto Peon
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Nico Williams
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Poul-Henning Kamp
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Phillip Hallam-Baker
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Nico Williams
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Nico Williams
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Poul-Henning Kamp
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Phillip Hallam-Baker
Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) Phillip Hallam-Baker
Re: moving forward on draft-lear-httpbis-svcinfo-rr Phillip Hallam-Baker
Re: moving forward on draft-lear-httpbis-svcinfo-rr Eliot Lear
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Nico Williams
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Nico Williams
Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) Nico Williams
RE: proposed WINDOW_UPDATE text for session flow control windows RUELLAN Herve
Re: #431: URI path starting with "//" Julian Reschke
Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) Julian Reschke
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Roberto Peon
Re: Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Poul-Henning Kamp
Fwd: [httpbis] #432: Review Cachability of Status Codes WRT "Negative Caching" Mark Nottingham
HTTP/1.1 #223: Allowing heuristic caching for new status codes Mark Nottingham
Re: moving forward on draft-lear-httpbis-svcinfo-rr Mark Nottingham
Stateful compression of cookies (Re: Delta Compression and UTF-8 Header Values) Nico Williams
Re: Delta Compression and UTF-8 Header Values Phillip Hallam-Baker
Re: Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) Phillip Hallam-Baker
Re: Delta Compression and UTF-8 Header Values Nico Williams
Re: Delta Compression and UTF-8 Header Values Nico Williams
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Nico Williams
Re: Delta Compression and UTF-8 Header Values Nico Williams

Sunday, 10 February 2013

Re: Delta Compression and UTF-8 Header Values Zhong Yu
Re: Delta Compression and UTF-8 Header Values Zhong Yu
Re: Delta Compression and UTF-8 Header Values Zhong Yu
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Zhong Yu
Unicode sucks, get over it (Re: Delta Compression and UTF-8 Header Values) Nico Williams
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: http/2 prioritization/fairness bug with proxies Mike Belshe
Re: moving forward on draft-lear-httpbis-svcinfo-rr Mike Belshe
Re: Delta Compression and UTF-8 Header Values Roberto Peon
Re: proposed WINDOW_UPDATE text for session flow control windows 陈智昌
Re: #431: URI path starting with "//" Julian Reschke
Re: Using Github for HTTP2 陈智昌
Re: #431: URI path starting with "//" Zhong Yu
Re: #431: URI path starting with "//" Julian Reschke
Re: proposed WINDOW_UPDATE text for session flow control windows Patrick McManus
Re: Delta Compression and UTF-8 Header Values Mark Nottingham
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Willy Tarreau
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Willy Tarreau
Re: Using Github for HTTP2 Mark Nottingham
Re: Delta Compression and UTF-8 Header Values Julian Reschke
Re: Delta Compression and UTF-8 Header Values Julian Reschke
Re: Delta Compression and UTF-8 Header Values Julian Reschke
Re: Using Github for HTTP2 Julian Reschke
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Roberto Peon
Re: Delta Compression and UTF-8 Header Values Nico Williams
proposed WINDOW_UPDATE text for session flow control windows 陈智昌
Re: Delta Compression and UTF-8 Header Values Roberto Peon
Re: Delta Compression and UTF-8 Header Values Frédéric Kayser
Re: Using Github for HTTP2 陈智昌
Re: Delta Compression and UTF-8 Header Values James M Snell
Re: Delta Compression and UTF-8 Header Values Willy Tarreau
Re: Delta Compression and UTF-8 Header Values Roberto Peon
Re: Delta Compression and UTF-8 Header Values Frédéric Kayser
Re: Delta Compression and UTF-8 Header Values James M Snell
Re: Delta Compression and UTF-8 Header Values Frédéric Kayser
Re: Delta Compression and UTF-8 Header Values Roberto Peon
Re: Delta Compression and UTF-8 Header Values Martin J. Dürst
Re: Delta Compression and UTF-8 Header Values Martin J. Dürst
Re: Delta Compression and UTF-8 Header Values Martin J. Dürst

Saturday, 9 February 2013

Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Adrien W. de Croy
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Nico Williams
Re: Delta Compression and UTF-8 Header Values Willy Tarreau
Re: Delta Compression and UTF-8 Header Values Willy Tarreau
Re: Delta Compression and UTF-8 Header Values Albert Lunde
Re: Delta Compression and UTF-8 Header Values Martin Nilsson
Re: Delta Compression and UTF-8 Header Values Martin Nilsson
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Willy Tarreau
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values Martin J. Dürst
Re: Delta Compression and UTF-8 Header Values Martin J. Dürst
Re: Delta Compression and UTF-8 Header Values Bjoern Hoehrmann
Re: Delta Compression and UTF-8 Header Values Adrien W. de Croy
Re: Delta Compression and UTF-8 Header Values James M Snell

Friday, 8 February 2013

Re: Delta Compression and UTF-8 Header Values Mark Nottingham
Re: #431: URI path starting with "//" Zhong Yu
Re: Delta Compression and UTF-8 Header Values James M Snell
Re: Delta Compression and UTF-8 Header Values Roberto Peon
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Re: Delta Compression and UTF-8 Header Values James M Snell
Re: Delta Compression and UTF-8 Header Values Poul-Henning Kamp
Delta Compression and UTF-8 Header Values James M Snell
Re: #431: URI path starting with "//" Julian Reschke
Re: #430 / #268 - definition of "public" Amos Jeffries
Re: Framing and control-frame continuations Roberto Peon
Re: #430 / #268 - definition of "public" Roy T. Fielding
Re: Framing and control-frame continuations Adrien W. de Croy
Re: Framing and control-frame continuations Roberto Peon
Re: Framing and control-frame continuations Martin Nilsson
Re: http/2 prioritization/fairness bug with proxies Roberto Peon
Re: http/2 prioritization/fairness bug with proxies Ashok Kumar
Re: Framing and control-frame continuations Roberto Peon
Re: Framing and control-frame continuations Amos Jeffries
Using Github for HTTP2 Mark Nottingham

Thursday, 7 February 2013

Re: Framing and control-frame continuations James M Snell
Re: Framing and control-frame continuations David Morris
Re: httpbis - Requested session has been scheduled for IETF 86 Mark Nottingham
Fwd: httpbis - Requested session has been scheduled for IETF 86 Mark Nottingham
Re: Framing and control-frame continuations James M Snell
Re: Framing and control-frame continuations Martin Thomson
Re: Framing and control-frame continuations Eliot Lear
Re: Framing and control-frame continuations James M Snell
Re: Framing and control-frame continuations Patrick McManus
Re: Framing and control-frame continuations Patrick McManus
Re: Framing and control-frame continuations 陈智昌
Re: Framing and control-frame continuations Adrien W. de Croy
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Patrick McManus
Re: Framing and control-frame continuations Amos Jeffries
Re: Minutes from the Tokyo interim meeting Mark Nottingham
Re: Framing and control-frame continuations Ilari Liusvaara
Re: Framing and control-frame continuations Amos Jeffries
Re: Framing and control-frame continuations Ilari Liusvaara
New version of [TLS} Application Layer Protocol Negotiation Brian Raymor (MS OPEN TECH)
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Amos Jeffries
Re: Framing and control-frame continuations Amos Jeffries
Re: Framing and control-frame continuations Amos Jeffries

Wednesday, 6 February 2013

Re: Framing and control-frame continuations Mark Nottingham
Re: Framing and control-frame continuations Bjoern Hoehrmann
Re: Framing and control-frame continuations Adrien W. de Croy
Re: Framing and control-frame continuations James M Snell
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Adrien W. de Croy
Re: Framing and control-frame continuations Mark Nottingham
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations James M Snell
RE: Outstanding Action Items Gabriel Montenegro
Re: Framing and control-frame continuations Roberto Peon
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Roberto Peon
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Bjoern Hoehrmann
Re: Framing and control-frame continuations James M Snell
Re: Framing and control-frame continuations Brian Pane
Re: Framing and control-frame continuations Ilari Liusvaara
Re: Framing and control-frame continuations Roberto Peon
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Roland Zink
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Brian Pane
Re: Framing and control-frame continuations Roland Zink
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Roberto Peon
Re: Framing and control-frame continuations Roberto Peon
Re: Framing and control-frame continuations Roland Zink
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Martin Thomson
Re: Framing and control-frame continuations Amos Jeffries
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Mark Nottingham
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Framing and control-frame continuations Poul-Henning Kamp
Re: Outstanding Action Items 陈智昌
Re: moving forward on draft-lear-httpbis-svcinfo-rr Roberto Peon
Re: moving forward on draft-lear-httpbis-svcinfo-rr Martin J. Dürst

Tuesday, 5 February 2013

Re: Outstanding Action Items Roberto Peon
Framing and control-frame continuations Roberto Peon
Re: moving forward on draft-lear-httpbis-svcinfo-rr Roberto Peon
Re: moving forward on draft-lear-httpbis-svcinfo-rr Mark Nottingham
Re: moving forward on draft-lear-httpbis-svcinfo-rr James M Snell
Re: Outstanding Action Items Mark Nottingham
Re: Outstanding Action Items Roberto Peon
Re: moving forward on draft-lear-httpbis-svcinfo-rr 陈智昌
Re: moving forward on draft-lear-httpbis-svcinfo-rr Roberto Peon
Re: moving forward on draft-lear-httpbis-svcinfo-rr Eliot Lear
Re: moving forward on draft-lear-httpbis-svcinfo-rr Roberto Peon
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Roberto Peon
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Zhong Yu
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Bjoern Hoehrmann
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Martin Thomson
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Martin Thomson
moving forward on draft-lear-httpbis-svcinfo-rr Eliot Lear
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Poul-Henning Kamp
Re: Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] James M Snell
Re: Next Steps for HTTP/2.0 Mark Nottingham
Re: Next Steps for HTTP/2.0 James M Snell
Request Routing Information [was: Do we kill the "Host:" header in HTTP/2 ?] Mark Nottingham
Lucky 13 TLS Attack... James M Snell
Outstanding Action Items Mark Nottingham
Next Steps for HTTP/2.0 Mark Nottingham
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: URI path starting with "//" Mark Nottingham
Minutes from the Tokyo interim meeting Mark Nottingham

Monday, 4 February 2013

Re: http/2 prioritization/fairness bug with proxies Patrick McManus
Re: URI path starting with "//" Karl Dubost
Re: http/2 prioritization/fairness bug with proxies Poul-Henning Kamp
Re: http/2 prioritization/fairness bug with proxies Ben Niven-Jenkins
Re: http/2 prioritization/fairness bug with proxies Poul-Henning Kamp
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: http/2 prioritization/fairness bug with proxies James M Snell
Re: http/2 prioritization/fairness bug with proxies Nico Williams
Re: http/2 prioritization/fairness bug with proxies Nico Williams
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: http/2 prioritization/fairness bug with proxies 陈智昌
Re: http/2 prioritization/fairness bug with proxies Albert Lunde
Re: http/2 prioritization/fairness bug with proxies Amos Jeffries
Re: http/2 prioritization/fairness bug with proxies Mark Nottingham
Re: http/2 prioritization/fairness bug with proxies Amos Jeffries
Re: http/2 prioritization/fairness bug with proxies Ilya Grigorik
Re: http/2 prioritization/fairness bug with proxies Poul-Henning Kamp
Re: http/2 prioritization/fairness bug with proxies Mark Nottingham
Re: http/2 prioritization/fairness bug with proxies Yoav Nir
http/2 prioritization/fairness bug with proxies 陈智昌

Sunday, 3 February 2013

Re: Do we kill the "Host:" header in HTTP/2 ? Eliezer Croitoru
Re: #430 / #268 - definition of "public" Julian Reschke
Re: [Technical Errata Reported] RFC6266 (3475) Julian Reschke

Saturday, 2 February 2013

Re: Do we kill the "Host:" header in HTTP/2 ? Mark Baker
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
#431: URI path starting with "//" Julian Reschke
Re: URI path starting with "//" Nico Williams

Friday, 1 February 2013

Re: Do we kill the "Host:" header in HTTP/2 ? Adrien de Croy
Re: URI path starting with "//" Zhong Yu
Re: URI path starting with "//" Eliezer Croitoru
Re: URI path starting with "//" Phillip Hallam-Baker
Re: URI path starting with "//" Julian Reschke
Re: URI path starting with "//" Phillip Hallam-Baker
Re: URI path starting with "//" Tim Bray
Re: Do we kill the "Host:" header in HTTP/2 ? James M Snell
Re: URI path starting with "//" Roy T. Fielding
Re: URI path starting with "//" Julian Reschke
Re: Do we kill the "Host:" header in HTTP/2 ? Adrien de Croy
Re: Do we kill the "Host:" header in HTTP/2 ? Julian Reschke
Re: Do we kill the "Host:" header in HTTP/2 ? Adrien de Croy
Re: URI path starting with "//" Bjoern Hoehrmann
Re: URI path starting with "//" Julian Reschke
URI path starting with "//" Zhong Yu
Re: Do we kill the "Host:" header in HTTP/2 ? Roland Zink
Re: Do we kill the "Host:" header in HTTP/2 ? James M Snell
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? James M Snell
Re: Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? Karl Dubost
Re: Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? Julian Reschke
Re: Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? Cyrus Daboo
Methods unique token Re: Do we kill the "Host:" header in HTTP/2 ? Karl Dubost
Re: Do we kill the "Host:" header in HTTP/2 ? James M Snell
Re: Do we kill the "Host:" header in HTTP/2 ? Nico Williams
Re: Do we kill the "Host:" header in HTTP/2 ? James M Snell
Re: Do we kill the "Host:" header in HTTP/2 ? Willy Tarreau
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Adrien W. de Croy
Re: HTTP/2.0 Magic Amos Jeffries
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Amos Jeffries
Re: HTTP/2.0 Magic Roy T. Fielding
Re: HTTP/2.0 Magic Roy T. Fielding
Re: HTTP/2.0 Magic David Morris
Re: HTTP/2.0 Magic Willy Tarreau
Re: HTTP/2.0 Magic James M Snell
Re: HTTP/2.0 Magic Roy T. Fielding
Re: Do we kill the "Host:" header in HTTP/2 ? James M Snell
Re: HTTP/2.0 Magic Martin Thomson
Re: HTTP/2.0 Magic Frédéric Kayser
Re: HTTP/2.0 Magic Chris Elving
Re: HTTP/2.0 Magic Dr Robert Mattson
Re: HTTP/2.0 Magic Eliot Lear
Re: HTTP/2.0 Magic Adrien W. de Croy
Re: HTTP/2.0 Magic Eliot Lear
Re: HTTP/2.0 Magic Roberto Peon
HTTP/2.0 Magic Martin Thomson

Thursday, 31 January 2013

Re: Do we kill the "Host:" header in HTTP/2 ? Ted Hardie
Re: Do we kill the "Host:" header in HTTP/2 ? Roy T. Fielding
Re: Do we kill the "Host:" header in HTTP/2 ? Eliezer Croitoru
Re: #430 / #268 - definition of "public" Roy T. Fielding
RE: Do we kill the "Host:" header in HTTP/2 ? RUELLAN Herve
Re: #430 / #268 - definition of "public" Adrien W. de Croy
Re: #430 / #268 - definition of "public" David Morris
Re: Do we kill the "Host:" header in HTTP/2 ? Zhong Yu
Re: #430 / #268 - definition of "public" Martin Thomson
Re: #430 / #268 - definition of "public" Patrick McManus
Re: #430 / #268 - definition of "public" Roy T. Fielding
Re: Do we kill the "Host:" header in HTTP/2 ? Adrien W. de Croy
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Re: Do we kill the "Host:" header in HTTP/2 ? Willy Tarreau
RE: Do we kill the "Host:" header in HTTP/2 ? RUELLAN Herve
RE: Do we kill the "Host:" header in HTTP/2 ? RUELLAN Herve

Wednesday, 30 January 2013

Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Patrick McManus
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Nico Williams
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
RE: Do we kill the "Host:" header in HTTP/2 ? Larry Masinter
Re: Do we kill the "Host:" header in HTTP/2 ? James M Snell
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Re: Do we kill the "Host:" header in HTTP/2 ? Adrien W. de Croy
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Willy Tarreau
Re: Do we kill the "Host:" header in HTTP/2 ? Ted Hardie
Re: #430 / #268 - definition of "public" David Morris
Re: Do we kill the "Host:" header in HTTP/2 ? Nico Williams
Re: Do we kill the "Host:" header in HTTP/2 ? Adrien W. de Croy
Re: #430 / #268 - definition of "public" Adrien W. de Croy
Re: Do we kill the "Host:" header in HTTP/2 ? Eliezer Croitoru
Re: #430 / #268 - definition of "public" Roy T. Fielding
Re: Do we kill the "Host:" header in HTTP/2 ? Nico Williams
#430 / #268 - definition of "public" Mark Nottingham
Re: Do we kill the "Host:" header in HTTP/2 ? Patrick McManus
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Julian Reschke
Re: Do we kill the "Host:" header in HTTP/2 ? Julian Reschke
Re: Do we kill the "Host:" header in HTTP/2 ? Amos Jeffries
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Re: Do we kill the "Host:" header in HTTP/2 ? Roland Zink
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Re: Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp
Re: Do we kill the "Host:" header in HTTP/2 ? Roberto Peon
Do we kill the "Host:" header in HTTP/2 ? Poul-Henning Kamp

Tuesday, 29 January 2013

Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Karl Dubost
Re: Should Web Services be served by a different HTTP n+1? Yoav Nir
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon

Monday, 28 January 2013

Re: Should Web Services be served by a different HTTP n+1? Hassnaa Moustafa
Re: can a conditional header field put conditions on resources other than the target resource? Julian Reschke
Re: can a conditional header field put conditions on resources other than the target resource? Amos Jeffries
Re: can a conditional header field put conditions on resources other than the target resource? Julian Reschke
Re: http/2 flow control Mike Belshe
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Martin J. Dürst
Re: [httpbis] #223: Allowing heuristic caching for new status codes Roy T. Fielding

Sunday, 27 January 2013

Re: can a conditional header field put conditions on resources other than the target resource? Amos Jeffries
Re: [httpbis] #223: Allowing heuristic caching for new status codes Mark Nottingham

Friday, 25 January 2013

Re: can a conditional header field put conditions on resources other than the target resource? Julian Reschke
Re: can a conditional header field put conditions on resources other than the target resource? Roy T. Fielding
can a conditional header field put conditions on resources other than the target resource? Julian Reschke
Re: #96 Conditional GET text Roy T. Fielding
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
#96 Conditional GET text Julian Reschke
Re: http/2 flow control Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Martin J. Dürst
Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" Amos Jeffries
Header compression: http1_huffman Frédéric Kayser
Re: Should Web Services be served by a different HTTP n+1? 陈智昌
Re: Should Web Services be served by a different HTTP n+1? 陈智昌
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? 陈智昌
RE: Should Web Services be served by a different HTTP n+1? Robert Brewer

Thursday, 24 January 2013

Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: http/2 flow control Roberto Peon
Re: http/2 flow control Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
http/2 flow control 陈智昌
Re: Should Web Services be served by a different HTTP n+1? Yoav Nir
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
Re: Should Web Services be served by a different HTTP n+1? Yoav Nir
Re: Should Web Services be served by a different HTTP n+1? Mark Nottingham
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: Types of Web Service Phillip Hallam-Baker
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: Types of Web Service Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? 陈智昌
Re: Should Web Services be served by a different HTTP n+1? Roberto Peon
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Re: Should Web Services be served by a different HTTP n+1? Nico Williams
Types of Web Service Phillip Hallam-Baker
Re: Should Web Services be served by a different HTTP n+1? 陈智昌
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" Zhong Yu
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" Julian Reschke
Re: Should Web Services be served by a different HTTP n+1? Grahame Grieve
Re: delta encoding and state management Willy Tarreau
Re: delta encoding and state management Patrick McManus
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: delta encoding and state management Patrick McManus
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: delta encoding and state management Willy Tarreau
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Re: delta encoding and state management Benjamin Carlyle
Re: Should Web Services be served by a different HTTP n+1? Greg Wilkins
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" Mark Nottingham

Wednesday, 23 January 2013

Re: Status of 308 Status Code draft Bjoern Hoehrmann
Status of 308 Status Code draft Piotr Dobrogost
Re: delta encoding and state management Patrick McManus
Re: delta encoding and state management Poul-Henning Kamp
Re: delta encoding and state management Patrick McManus
state management on connections Stefan Eissing
RE: Header Stats RUELLAN Herve
HTTP/2.0 Max Frame Size Osama Mazahir
Re: delta encoding and state management Willy Tarreau
Re: Header Stats James M Snell
Re: delta encoding and state management 陈智昌
Re: delta encoding and state management Willy Tarreau

Tuesday, 22 January 2013

Re: delta encoding and state management 陈智昌
Re: delta encoding and state management Willy Tarreau
Re: delta encoding and state management Roberto Peon
Re: delta encoding and state management Willy Tarreau
Re: delta encoding and state management Roberto Peon
Re: delta encoding and state management Roberto Peon
Re: delta encoding and state management 陈智昌
Re: delta encoding and state management Willy Tarreau
Header Stats James M Snell
Re: delta encoding and state management 陈智昌
Re: [apps-discuss] New Version Notification for draft-wilde-xml-patch-00.txt Nicholas Shanks
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Roberto Peon
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Patrick McManus
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Nicholas Shanks
Re: #428 Accept-Language ordering for identical qvalues Adrien W. de Croy
Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Re: #428 Accept-Language ordering for identical qvalues Adrien W. de Croy
Re: The use of binary data in any part of HTTP 2.0 is not good Roberto Peon
Re: The use of binary data in any part of HTTP 2.0 is not good Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Roberto Peon
Re: The use of binary data in any part of HTTP 2.0 is not good Adrien W. de Croy
Re: #428 Accept-Language ordering for identical qvalues Adrien W. de Croy
Re: The use of binary data in any part of HTTP 2.0 is not good Nico Williams
Re: The use of binary data in any part of HTTP 2.0 is not good Amos Jeffries
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Frédéric Kayser
Re: #428 Accept-Language ordering for identical qvalues James M Snell
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Roberto Peon
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Ilya Grigorik
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Mark Nottingham
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Roberto Peon
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Mark Nottingham
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Roberto Peon
Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) 陈智昌
How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt) Frédéric Kayser

Monday, 21 January 2013

-01 posted Martin Thomson
I-D Action: draft-ietf-httpbis-http2-01.txt internet-drafts@ietf.org
Re: Interim Meeting - next week Barry Leiba
Re: The use of binary data in any part of HTTP 2.0 is not good Patrick McManus
Re: The use of binary data in any part of HTTP 2.0 is not good Patrick McManus
Re: #428 Accept-Language ordering for identical qvalues Nicholas Shanks
RE: bohe and delta experimentation... RUELLAN Herve
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: The use of binary data in any part of HTTP 2.0 is not good Eliot Lear
Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Interim Meeting - next week Mark Nottingham
Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: The use of binary data in any part of HTTP 2.0 is not good Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: The use of binary data in any part of HTTP 2.0 is not good Mark Nottingham
Re: #429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Willy Tarreau
Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: #429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Mark Nottingham
Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: The use of binary data in any part of HTTP 2.0 is not good Adrien W. de Croy
Re: The use of binary data in any part of HTTP 2.0 is not good Mark Nottingham
Re: The use of binary data in any part of HTTP 2.0 is not good Nico Williams

Sunday, 20 January 2013

Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: The use of binary data in any part of HTTP 2.0 is not good Mark Nottingham
Re: The use of binary data in any part of HTTP 2.0 is not good Mark Nottingham
Re: The use of binary data in any part of HTTP 2.0 is not good Roberto Peon
Re: The use of binary data in any part of HTTP 2.0 is not good Amos Jeffries
Re: The use of binary data in any part of HTTP 2.0 is not good Adrien W. de Croy
Re: The use of binary data in any part of HTTP 2.0 is not good James M Snell
Re: #428 Accept-Language ordering for identical qvalues Adrien W. de Croy
Re: The use of binary data in any part of HTTP 2.0 is not good Tim Bray
Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: The use of binary data in any part of HTTP 2.0 is not good David Morris
Re: The use of binary data in any part of HTTP 2.0 is not good Amos Jeffries
Re: The use of binary data in any part of HTTP 2.0 is not good Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues James M Snell
Re: The use of binary data in any part of HTTP 2.0 is not good 陈智昌
Re: The use of binary data in any part of HTTP 2.0 is not good Willy Tarreau
The use of binary data in any part of HTTP 2.0 is not good Pablo
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Re: #409: is parsing OBS-FOLD mandatory? Willy Tarreau
Re: #409: is parsing OBS-FOLD mandatory? Mark Nottingham
Re: Lingering Close Willy Tarreau
Re: #409: is parsing OBS-FOLD mandatory? Willy Tarreau
Re: #429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Willy Tarreau
Re: Lingering Close Mark Nottingham
#429: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Mark Nottingham
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Mark Nottingham
Re: #409: is parsing OBS-FOLD mandatory? Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Mark Nottingham
Re: Set-Cookie and Cookie Optimized Binary Encoding Nico Williams
Re: Set-Cookie and Cookie Optimized Binary Encoding James M Snell
Re: Set-Cookie and Cookie Optimized Binary Encoding Nico Williams
Re: Set-Cookie and Cookie Optimized Binary Encoding James M Snell

Saturday, 19 January 2013

Re: Set-Cookie and Cookie Optimized Binary Encoding Mark Nottingham
Re: delta encoding and state management Mark Nottingham
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: Cache-Cache and Binary Encoding Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Adrien W. de Croy
Re: #428 Accept-Language ordering for identical qvalues Adrien W. de Croy
Re: #428 Accept-Language ordering for identical qvalues Nico Williams
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: bohe and delta experimentation... Adrien W. de Croy

Friday, 18 January 2013

Re: bohe and delta experimentation... Poul-Henning Kamp
Cache-Cache and Binary Encoding James M Snell
Re: Set-Cookie and Cookie Optimized Binary Encoding Martin Thomson
Re: bohe and delta experimentation... Willy Tarreau
Re: bohe and delta experimentation... Phillip Hallam-Baker
Re: bohe and delta experimentation... Roberto Peon
Re: Set-Cookie and Cookie Optimized Binary Encoding James M Snell
Re: bohe and delta experimentation... Martin Nilsson
Re: bohe and delta experimentation... Willy Tarreau
Re: Set-Cookie and Cookie Optimized Binary Encoding Martin Thomson
Set-Cookie and Cookie Optimized Binary Encoding James M Snell
RE: bohe and delta experimentation... Roberto Peon
Re: bohe and delta experimentation... Willy Tarreau
Re: bohe and delta experimentation... Willy Tarreau
RE: bohe and delta experimentation... RUELLAN Herve
RE: delta encoding and state management RUELLAN Herve
Re: #428 Accept-Language ordering for identical qvalues Nicholas Shanks
Re: The document's address Roy T. Fielding
Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Re: The document's address Nicholas Shanks
Re: bohe and delta experimentation... Poul-Henning Kamp
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Martin J. Dürst
Re: bohe and delta experimentation... Amos Jeffries
Re: bohe and delta experimentation... Amos Jeffries
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Amos Jeffries
Re: bohe and delta experimentation... Frédéric Kayser
Re: bohe and delta experimentation... Mark Nottingham
Re: bohe and delta experimentation... Martin J. Dürst
Re: bohe implementation for compression tests Mark Nottingham
Re: bohe and delta experimentation... Martin J. Dürst

Thursday, 17 January 2013

Re: delta encoding and state management James M Snell
Re: delta encoding and state management Nico Williams
Re: delta encoding and state management Roberto Peon
Re: delta encoding and state management Adrien W. de Croy
Re: delta encoding and state management Willy Tarreau
Re: delta encoding and state management James M Snell
Re: delta encoding and state management Nico Williams
Re: delta encoding and state management Roberto Peon
Re: delta encoding and state management Mark Nottingham
Re: delta encoding and state management Nico Williams
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: delta encoding and state management Roberto Peon
Re: bohe and delta experimentation... Nico Williams
Re: delta encoding and state management Nico Williams
Re: delta encoding and state management Roberto Peon
Re: bohe and delta experimentation... Frédéric Kayser
Re: delta encoding and state management James M Snell
Re: delta encoding and state management Roberto Peon
Re: delta encoding and state management Martin Thomson
Re: delta encoding and state management Nico Williams
Re: delta encoding and state management Nico Williams
Re: delta encoding and state management James M Snell
Re: delta encoding and state management Nico Williams
Re: delta encoding and state management James M Snell
RE: bohe and delta experimentation... RUELLAN Herve
Re: bohe and delta experimentation... Poul-Henning Kamp
Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Julian Reschke
Re: #428 Accept-Language ordering for identical qvalues Roy T. Fielding
Re: #428 Accept-Language ordering for identical qvalues Martin J. Dürst
Re: Heuristic caching without validators Roy T. Fielding
Re: Heuristic caching without validators Mark Nottingham
Re: bohe implementation for compression tests Mark Nottingham
Re: bohe implementation for compression tests Roberto Peon
Re: delta encoding and state management Roberto Peon
delta encoding and state management James M Snell
Re: Heuristic caching without validators Adrien W. de Croy
Re: bohe implementation for compression tests Martin Thomson
Re: bohe and delta experimentation... Martin Thomson
Re: bohe and delta experimentation... Martin Thomson
Re: bohe and delta experimentation... Patrick McManus
Re: bohe implementation for compression tests Mark Nottingham
Re: Heuristic caching without validators Mark Nottingham
Re: bohe implementation for compression tests Roberto Peon
Re: bohe implementation for compression tests Martin Thomson
Re: Some general thought on CRIME and Compression and Headers Martin Thomson
Re: bohe and delta experimentation... Mark Nottingham
Re: Should Web Services be served by a different HTTP n+1? Martin Thomson
Re: bohe and delta experimentation... Nico Williams
Re: bohe and delta experimentation... James M Snell
Heuristic caching without validators Adrien W. de Croy
Re: bohe and delta experimentation... Mark Nottingham
Re: bohe and delta experimentation... Roberto Peon
Re: bohe and delta experimentation... James M Snell

Wednesday, 16 January 2013

Re: bohe and delta experimentation... Nico Williams
Re: bohe and delta experimentation... Roberto Peon
Re: bohe and delta experimentation... Roberto Peon
Re: bohe and delta experimentation... James M Snell
Re: bohe and delta experimentation... Nico Williams
Re: bohe and delta experimentation... Mark Nottingham
Re: bohe and delta experimentation... Nico Williams
Re: bohe and delta experimentation... Mark Nottingham
Re: bohe and delta experimentation... Nico Williams
Re: bohe and delta experimentation... Nico Williams
Re: bohe and delta experimentation... Roberto Peon
Re: bohe and delta experimentation... James M Snell
Re: bohe and delta experimentation... Mark Nottingham
Re: bohe and delta experimentation... Nico Williams
Re: bohe and delta experimentation... James M Snell
Re: bohe and delta experimentation... Mark Nottingham
bohe and delta experimentation... James M Snell
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Nico Williams
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Willy Tarreau
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Zhong Yu
#428 Accept-Language ordering for identical qvalues Julian Reschke
RE: FYI: Tools to evaluate header compression algorithms RUELLAN Herve
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Amos Jeffries
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Willy Tarreau
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Karl Dubost
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Zhong Yu
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Roy T. Fielding
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Julian Reschke
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Zhong Yu
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Nico Williams
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Julian Reschke
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Nico Williams
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Mark Nottingham

Tuesday, 15 January 2013

Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Nico Williams
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Mark Nottingham
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Piotr Dobrogost
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Nico Williams
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Mark Nottingham
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Nico Williams
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Mark Nottingham
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Bjoern Hoehrmann
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Willy Tarreau
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Julian Reschke
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Karl Dubost
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Julian Reschke
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Piotr Dobrogost
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Julian Reschke
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Karl Dubost
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Poul-Henning Kamp
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Julian Reschke
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Zhong Yu
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Julian Reschke
Draft agenda for Interim Meeting Mark Nottingham
Re: Multiple header fields with the same field name - unwritten assumption about quoted commas in values? Piotr Dobrogost
Re: bohe implementation for compression tests James M Snell
Re: bohe implementation for compression tests Roberto Peon
Re: bohe implementation for compression tests James M Snell
Re: bohe implementation for compression tests Roberto Peon
Re: bohe implementation for compression tests James M Snell

Monday, 14 January 2013

Re: FYI: Tools to evaluate header compression algorithms Mark Nottingham
Re: FYI: Tools to evaluate header compression algorithms James M Snell
Re: FYI: Tools to evaluate header compression algorithms Frédéric Kayser
Re: HTTPS, proxying, and all that... James M Snell
Re: HTTPS, proxying, and all that... Roberto Peon
Re: HTTPS, proxying, and all that... James M Snell
Session Continuation at WebSec Yoav Nir
Re: HTTPS, proxying, and all that... Nico Williams
Re: Some general thought on CRIME and Compression and Headers Nico Williams
Re: FYI: Tools to evaluate header compression algorithms James M Snell
Re: HTTPS, proxying, and all that... Stephane Bortzmeyer
Re: FYI: Tools to evaluate header compression algorithms Mark Nottingham
Re: WGLC review of p2-semantics (editorial stuff) Roy T. Fielding

Saturday, 12 January 2013

Re: Some general thought on CRIME and Compression and Headers Poul-Henning Kamp
Re: Some general thought on CRIME and Compression and Headers Roberto Peon
Re: Some general thought on CRIME and Compression and Headers Frédéric Kayser
Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-02.txt Tim Bray

Friday, 11 January 2013

Re: HTTPS, proxying, and all that... Poul-Henning Kamp
Re: HTTPS, proxying, and all that... Eliot Lear
Re: HTTPS, proxying, and all that... Stephen Farrell
Re: HTTPS, proxying, and all that... Poul-Henning Kamp
Re: HTTPS, proxying, and all that... Poul-Henning Kamp
Re: HTTPS, proxying, and all that... Stephen Farrell
Re: HTTPS, proxying, and all that... Yoav Nir
Re: HTTPS, proxying, and all that... Poul-Henning Kamp
Re: Should Web Services be served by a different HTTP n+1? James M Snell
Re: HTTPS, proxying, and all that... Poul-Henning Kamp
Re: Should Web Services be served by a different HTTP n+1? Tim Bray
Re: HTTPS, proxying, and all that... Stephen Farrell
Should Web Services be served by a different HTTP n+1? Phillip Hallam-Baker
Re: HTTPS, proxying, and all that... Yoav Nir
Re: HTTPS, proxying, and all that... Poul-Henning Kamp
Some general thought on CRIME and Compression and Headers James M Snell
Re: HTTPS, proxying, and all that... Stephen Farrell
Re: HTTPS, proxying, and all that... Poul-Henning Kamp
Re: HTTPS, proxying, and all that... Ilya Grigorik
Re: bohe implementation for compression tests James M Snell
HTTPS, proxying, and all that... Poul-Henning Kamp

Thursday, 10 January 2013

Re: bohe implementation for compression tests James M Snell
Re: bohe implementation for compression tests Roberto Peon
bohe implementation for compression tests James M Snell
Re: FYI: Tools to evaluate header compression algorithms Martin Nilsson

Wednesday, 9 January 2013

Tuesday, 8 January 2013

Re: [editorial] awkward sentence for a MUST statement in section 6.3 Upgrade Julian Reschke
Re: [editorial] awkward sentence for a MUST statement in section 6.3 Upgrade Barry Leiba
[editorial] awkward sentence for a MUST statement in section 6.3 Upgrade Karl Dubost
Re: draft-snell-http-prefer-17 feedback Barry Leiba

Monday, 7 January 2013

Re: draft-snell-http-prefer-17 feedback James M Snell
Re: FYI: Tools to evaluate header compression algorithms Roberto Peon
Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable" Yves Lafon
Re: FYI: Tools to evaluate header compression algorithms Mark Nottingham
Re: FYI: Tools to evaluate header compression algorithms Mark Nottingham

Sunday, 6 January 2013

Re: FYI: Tools to evaluate header compression algorithms Ilya Grigorik
Re: FYI: Tools to evaluate header compression algorithms Roberto Peon
Re: FYI: Tools to evaluate header compression algorithms Martin J. Dürst
Re: FYI: Tools to evaluate header compression algorithms Mark Nottingham

Friday, 4 January 2013

Re: WebDAV If header field and HTTP conditional precedence Julian Reschke
Re: draft-snell-http-prefer-17 feedback Barry Leiba

Thursday, 3 January 2013

httpbis Tim Williams

Last message date: Sunday, 31 March 2013 16:38:57 UTC