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

Sunday, 30 June 2013

Re: [#150] Making certain settings mandatory Eliot Lear
Re: #481, was: WGLC: p7 MUSTs Julian Reschke
Re: #481, was: WGLC: p7 MUSTs Alex Rousskov
Header compression question Gábor Molnár
Re: [#150] Making certain settings mandatory Jeff Pinner
Re: #481, was: WGLC: p7 MUSTs Julian Reschke
Re: #487 Resubmission of 403 Julian Reschke
Re: Ranges Julian Reschke

Saturday, 29 June 2013

Re: [#150] Making certain settings mandatory Eliot Lear
Re: HTTP Layer rework and PUSH_PROMISE contents Martin Thomson
Re: [#150] Making certain settings mandatory Roberto Peon
Re: [#150] Making certain settings mandatory Jeff Pinner
Re: [#150] Making certain settings mandatory Roberto Peon
Re: [#150] Making certain settings mandatory Jeff Pinner
Re: [#150] Making certain settings mandatory Roberto Peon
Re: [#150] Making certain settings mandatory Jeff Pinner
Re: [#150] Making certain settings mandatory Roberto Peon
Re: [#150] Making certain settings mandatory Jeff Pinner
Re: [#153] PUSH_PROMISE headers Jeff Pinner
Re: [#153] PUSH_PROMISE headers James M Snell
Re: [#153] PUSH_PROMISE headers Yoav Nir
Re: [#153] PUSH_PROMISE headers Amos Jeffries
Re: [#153] PUSH_PROMISE headers David Morris
Re: [#153] PUSH_PROMISE headers Roberto Peon
Re: [#153] PUSH_PROMISE headers James M Snell
Re: Issue #154: Sending a response before the request is complete Roberto Peon
Re: [#153] PUSH_PROMISE headers Roberto Peon
Issue #154: Sending a response before the request is complete James M Snell
Re: [#153] PUSH_PROMISE headers Roberto Peon
Re: [#153] PUSH_PROMISE headers James M Snell
Re: [#153] PUSH_PROMISE headers Roberto Peon
Re: [#153] PUSH_PROMISE headers James M Snell
RE: HTTP Layer rework and PUSH_PROMISE contents Mike Bishop
Re: HTTP Layer rework and PUSH_PROMISE contents David Morris
Re: HTTP Layer rework and PUSH_PROMISE contents Mike Belshe
Re: HTTP Layer rework and PUSH_PROMISE contents James M Snell
[#153] PUSH_PROMISE headers Martin Thomson
HTTP Layer rework and PUSH_PROMISE contents Mike Bishop

Friday, 28 June 2013

HTTP Mapping editorial changes Martin Thomson

Thursday, 27 June 2013

Re: [#150] Making certain settings mandatory Mike Belshe
Header compression, editorial Martin Thomson
[#150] Making certain settings mandatory Martin Thomson
Re: draft-snell-httpbis-mget: Proposal for a new SHORTER format to header field :path D R
draft-snell-httpbis-mget: Proposal for a new SHORTER format to header field :path D R
Re: ADMIN: Discussion on Github issues Mark Nottingham
Re: ADMIN: Discussion on Github issues Julian Reschke
ADMIN: Discussion on Github issues Mark Nottingham
Re: Rough Minutes from SF F2F Mark Nottingham
Ranges Adrien W. de Croy

Wednesday, 26 June 2013

Brief header compression comments Martin Thomson
Re: Outcomes of the SF Interim Meeting Martin Thomson
Re: Rough Minutes from SF F2F James M Snell
I-D Action: draft-ietf-httpbis-header-compression-00.txt internet-drafts@ietf.org
Outcomes of the SF Interim Meeting Mark Nottingham
Fwd: HTTPBIS WG Interim Meeting, August 5-7, 2013 Mark Nottingham
Re: Rough Minutes from SF F2F Mark Nottingham

Tuesday, 25 June 2013

Rough Minutes from SF F2F Mark Nottingham

Monday, 24 June 2013

Re: Summer of Code project Gábor Molnár
Re: Out-of-order Frames Roberto Peon
Re: Summer of Code project 陈智昌
Re: Is the ability to disable flow control really needed? Martin Thomson
Re: Out-of-order Frames Michael Sweet
Fwd: Summer of Code project Gábor Molnár
Re: Is the ability to disable flow control really needed? Fred Akalin
RE: Is the ability to disable flow control really needed? Gabriel Montenegro

Sunday, 23 June 2013

Saturday, 22 June 2013

Re: Out-of-order Frames 陈智昌
Re: Out-of-order Frames James M Snell
Re: Out-of-order Frames Mark Nottingham
Re: Out-of-order Frames Sam Pullara
Re: Out-of-order Frames Sam Pullara
Re: Out-of-order Frames David Morris
Re: Out-of-order Frames 陈智昌
Re: Out-of-order Frames Sam Pullara
Re: Out-of-order Frames 陈智昌
Re: Out-of-order Frames Sam Pullara
Re: Out-of-order Frames 陈智昌
Re: Out-of-order Frames Sam Pullara
Re: Out-of-order Frames 陈智昌
Out-of-order Frames Sam Pullara
Re: Questions on Frame Size Shigeki Ohtsu
Re: Is the ability to disable flow control really needed? Fred Akalin
Re: Is the ability to disable flow control really needed? Jeff Pinner
Re: Is the ability to disable flow control really needed? 陈智昌
Re: Is the ability to disable flow control really needed? Jeff Pinner
Re: Is the ability to disable flow control really needed? 陈智昌

Friday, 21 June 2013

Re: Is the ability to disable flow control really needed? Roberto Peon
Re: Is the ability to disable flow control really needed? Fred Akalin
Re: Is the ability to disable flow control really needed? Fred Akalin
Re: Is the ability to disable flow control really needed? Jeff Pinner
Re: Header Compression Roberto Peon
Re: Is the ability to disable flow control really needed? Martin Thomson
Is the ability to disable flow control really needed? Fred Akalin
Re: Questions on Frame Size Martin Thomson
Re: Questions on Frame Size Shigeki Ohtsu
Re: Questions on Frame Size 陈智昌
Re: Questions on Frame Size 陈智昌
Re: Questions on Frame Size James M Snell
Re: Questions on Frame Size Shigeki Ohtsu
Re: Design: Adding ASSOCIATED_ONLY Amos Jeffries
Re: Questions on Frame Size David Morris
Re: Questions on Frame Size Amos Jeffries

Thursday, 20 June 2013

Re: Header Compression Ted Hardie
Re: Questions on Frame Size Shigeki Ohtsu
Re: #462, was: p5: editorial suggestions Julian Reschke
#482l was: WGLC p1: proxy handling of a really bad Content-Length Julian Reschke
Re: Design: Adding ASSOCIATED_ONLY James M Snell
Re: #462, was: p5: editorial suggestions Mark Nottingham
#486, was: p2: Expectation extensions Julian Reschke
Re: #462, was: p5: editorial suggestions Julian Reschke
Re: Questions on Frame Size James M Snell
Re: Design: Adding ASSOCIATED_ONLY Amos Jeffries
Re: #462, was: p5: editorial suggestions Mark Nottingham
#487 Resubmission of 403 Julian Reschke
#462, was: p5: editorial suggestions Julian Reschke
DASH/XMPP workshop Eliot Lear
Re: Questions on Frame Size Shigeki Ohtsu
Re: Questions on Frame Size Roberto Peon
Questions on Frame Size Shigeki Ohtsu

Wednesday, 19 June 2013

Re: END_STREAM on PUSH_PROMISE James M Snell
Re: END_STREAM on PUSH_PROMISE Martin Thomson
END_STREAM on PUSH_PROMISE James M Snell
Re: Design: Adding ASSOCIATED_ONLY Mike Belshe
Re: Design: Adding ASSOCIATED_ONLY Martin Thomson
Re: Design: Adding ASSOCIATED_ONLY Patrick McManus
Re: Design: Adding ASSOCIATED_ONLY Jeff Pinner
Re: Design: Adding ASSOCIATED_ONLY James M Snell
Re: Design: Adding ASSOCIATED_ONLY Mike Belshe
Re: Design: Adding ASSOCIATED_ONLY Mike Belshe
Re: Design: Adding ASSOCIATED_ONLY 陈智昌
Re: Design: Adding ASSOCIATED_ONLY Mike Belshe
Re: Design: Adding ASSOCIATED_ONLY Jeff Pinner
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR 陈智昌
Re: Design: Adding ASSOCIATED_ONLY James M Snell
Re: Design: Adding ASSOCIATED_ONLY Patrick McManus
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Patrick McManus
Re: Design: Adding ASSOCIATED_ONLY Mike Belshe
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Martin Thomson
Re: Design: Adding ASSOCIATED_ONLY Martin Thomson
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR James M Snell
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Martin Thomson
Design: Adding ASSOCIATED_ONLY James M Snell
Re: GOAWAY(AND_DONT_COME_BACK) James M Snell
Re: GOAWAY(AND_DONT_COME_BACK) Poul-Henning Kamp
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR James M Snell
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR 陈智昌
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Martin Thomson
Re: Nit: Server-sent priority Mike Belshe
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Roberto Peon
Re: GOAWAY(AND_DONT_COME_BACK) Roberto Peon
Re: Nit: Server-sent priority Roberto Peon
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR James M Snell
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Jeff Pinner
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Roberto Peon
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Roberto Peon
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Jeff Pinner
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR James M Snell
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR David Morris
Re: Nit: Server-sent priority Patrick McManus
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Patrick McManus
Re: Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR Matthew Kerwin
Re: GOAWAY(AND_DONT_COME_BACK) Eliot Lear
Re: GOAWAY(AND_DONT_COME_BACK) Poul-Henning Kamp
Fwd: Nit: Server-sent priority Mike Belshe
Design: Rename FRAME_TOO_LARGE to FRAME_SIZE_ERROR James M Snell
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Martin Thomson
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Jeff Pinner
Re: GOAWAY(AND_DONT_COME_BACK) Roberto Peon
Re: GOAWAY(AND_DONT_COME_BACK) Roberto Peon
Re: GOAWAY(AND_DONT_COME_BACK) James M Snell
Re: Nit: Server-sent priority James M Snell
Re: GOAWAY(AND_DONT_COME_BACK) Roberto Peon
Re: GOAWAY(AND_DONT_COME_BACK) James M Snell

Tuesday, 18 June 2013

Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity James M Snell
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity James M Snell
Re: GOAWAY(AND_DONT_COME_BACK) Roberto Peon
RE: GOAWAY(AND_DONT_COME_BACK) Mike Bishop
Re: Nit: Server-sent priority Roberto Peon
Re: GOAWAY(AND_DONT_COME_BACK) David Morris
Nit: Server-sent priority Martin Thomson
Re: GOAWAY(AND_DONT_COME_BACK) Roberto Peon
Re: GOAWAY(AND_DONT_COME_BACK) Martin Thomson
GOAWAY(AND_DONT_COME_BACK) Roberto Peon
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Martin Thomson
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Jeff Pinner
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Roberto Peon
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Jeff Pinner
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Martin Thomson
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Jeff Pinner

Monday, 17 June 2013

RE: Multiple Headers Roberto Peon
RE: Multiple Headers RUELLAN Herve
RE: Header Compression RUELLAN Herve
RE: Header Compression RUELLAN Herve
RE: Multiple Headers David Morris
RE: Multiple Headers RUELLAN Herve
RE: Multiple Headers RUELLAN Herve

Sunday, 16 June 2013

Re: Multiple Headers Jeff Pinner
Re: Multiple Headers James M Snell
Multiple Headers Jeff Pinner
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Amos Jeffries
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Roberto Peon
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity James M Snell
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity James M Snell
Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity 陈智昌

Saturday, 15 June 2013

Re: Issue re. HTTP2 STREAM and HEADER block use same end bit polarity Mike Belshe
Issue re. HTTP2 STREAM and HEADER block use same end bit polarity David Morris
Re: draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion Julian Reschke
Re: PUT, If-Match, 412 - over-constrained? Julian Reschke

Wednesday, 12 June 2013

Re: [saag] Is the CA market broken? Eliot Lear
Is the CA market broken? Eliot Lear
Re: Until HTTP header when the representation will disappear in the future Amos Jeffries
Re: #448, was: p2: Accept-Language missing, empty or no match Julian Reschke
Re: Until HTTP header when the representation will disappear in the future Karl Dubost
Re: Until HTTP header when the representation will disappear in the future Amos Jeffries
Until HTTP header when the representation will disappear in the future Karl Dubost

Tuesday, 11 June 2013

Monday, 10 June 2013

duplicate parameters R S
Re: port #? Eliot Lear
Re: #448, was: p2: Accept-Language missing, empty or no match Mark Nottingham
Re: #448, was: p2: Accept-Language missing, empty or no match Julian Reschke
Re: port #? Mark Nottingham
Re: #448, was: p2: Accept-Language missing, empty or no match Mark Nottingham

Sunday, 9 June 2013

Re: Header Compression James M Snell
Re: #481, was: WGLC: p7 MUSTs Alex Rousskov
#481, was: WGLC: p7 MUSTs Julian Reschke
#474, was: WGLC p7: Parsing auth challenges Julian Reschke
#448, was: p2: Accept-Language missing, empty or no match Julian Reschke
Re: p6: Warning header field Mark Nottingham
p6: Warning header field Roy T. Fielding

Friday, 7 June 2013

Re: port #? Roberto Peon
Re: port #? Martin Thomson
Re: port #? Ted Hardie
Re: Header Compression Tatsuhiro Tsujikawa
Re: port #? Eliot Lear
Re: port #? Julian Reschke
port #? Eliot Lear

Thursday, 6 June 2013

Fwd: New Version Notification for draft-snell-httpbis-bohe-09.txt James M Snell
Re: draft-snell-http-prefer: Preference-Applied James M Snell
draft-snell-http-prefer: Preference-Applied Ken Murchison
Re: Header Compression Martin Thomson
RE: Header Compression RUELLAN Herve
Re: Header Compression Yoav Nir
Re: Header Compression Mark Nottingham

Wednesday, 5 June 2013

Re: Header Compression Ryan Hamilton
Re: Header Compression Martin Thomson
Re: Header Compression James M Snell
Header Compression RUELLAN Herve
Re: HTTP URI in the form of "http://example.com?query" Zhong Yu
Re: HTTP URI in the form of "http://example.com?query" Willy Tarreau
Re: #458: Requirements upon proxies for Expect Amos Jeffries

Tuesday, 4 June 2013

Re: Preliminary agenda for the SF Interim 陈智昌
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY 陈智昌
Re: Preliminary agenda for the SF Interim 陈智昌
Re: HTTP URI in the form of "http://example.com?query" Zhong Yu
Re: HTTP URI in the form of "http://example.com?query" Roy T. Fielding
Re: HTTP URI in the form of "http://example.com?query" Zhong Yu
Re: HTTP URI in the form of "http://example.com?query" Daniel Stenberg
Re: HTTP URI in the form of "http://example.com?query" Bjoern Hoehrmann
Re: HTTP URI in the form of "http://example.com?query" Julian Reschke
Re: HTTP URI in the form of "http://example.com?query" Roberto Peon
Re: HTTP URI in the form of "http://example.com?query" Julian Reschke
Re: HTTP URI in the form of "http://example.com?query" Roberto Peon
Re: HTTP URI in the form of "http://example.com?query" Julian Reschke
Re: #458: Requirements upon proxies for Expect Willy Tarreau
Re: #458: Requirements upon proxies for Expect Mark Nottingham
Re: Questions on Server Push Shigeki Ohtsu
Re: Questions on Server Push Shigeki Ohtsu
RE: Questions on Server Push Mike Bishop
Re: Questions on Server Push Martin Thomson
Re: Questions on Server Push Shigeki Ohtsu

Monday, 3 June 2013

HTTP URI in the form of "http://example.com?query" Zhong Yu
Re: HTTP/2.0 SETTINGS frame values 陈智昌
Re: Questions on Server Push Martin Thomson

Friday, 31 May 2013

Questions on Server Push Shigeki Ohtsu
Re: #458: Requirements upon proxies for Expect Willy Tarreau

Thursday, 30 May 2013

Re: p2: Expectation extensions Mark Nottingham
#458: Requirements upon proxies for Expect Mark Nottingham
Agenda for June Interim meeting Mark Nottingham

Wednesday, 29 May 2013

Re: I-D Action: draft-ietf-httpbis-http2-03.txt Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-http2-03.txt Martin Thomson
I-D Action: draft-ietf-httpbis-http2-03.txt internet-drafts@ietf.org
Re: HTTP in JSON Binary Encoding / Data Model Phillip Hallam-Baker
Re: HTTP in JSON Binary Encoding / Data Model James M Snell
HTTP in JSON Binary Encoding / Data Model Phillip Hallam-Baker
WGLC p1: Scope of https update Henry S. Thompson
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Leif Hedstrom
Re: #486: Requiring proxies to process warn-date Mark Nottingham
Re: #467: Expect: 100-continue and "final" status codes Mark Nottingham
Re: #467: Expect: 100-continue and "final" status codes Willy Tarreau
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Roberto Peon
Re: Expect: 100-continue and "final" status codes Peter Occil
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Jeff Pinner
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Roberto Peon
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Roberto Peon
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Adrien W. de Croy

Tuesday, 28 May 2013

Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Patrick McManus
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits 陈智昌
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Martin Thomson
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Adrien W. de Croy
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Martin Thomson
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Adrien W. de Croy
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits David Morris
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Roberto Peon
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Patrick McManus
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Roberto Peon
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Roberto Peon
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY 陈智昌
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits 陈智昌
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits James M Snell
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits Roberto Peon
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Jeff Pinner
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Martin Thomson
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits 陈智昌
Re: Proposal - Reduce HTTP2 frame length from 16 to 12 bits James M Snell
Re: #467: Expect: 100-continue and "final" status codes Michael Sweet
Re: #467: Expect: 100-continue and "final" status codes Zhong Yu
Proposal - Reduce HTTP2 frame length from 16 to 12 bits Patrick McManus
Re: HTTP/2.0 SETTINGS frame values Mark Nottingham
Re: HTTP/2.0 SETTINGS frame values Michael Welzl
HTTP/2.0 SETTINGS frame values Michael Welzl
Re: Design Issue: GZIP flag on DATA Frames Adrien W. de Croy
Re: #467: Expect: 100-continue and "final" status codes Willy Tarreau
Re: Design Issue: GZIP flag on DATA Frames Mark Nottingham
Re: Caching 412 responses Ben Niven-Jenkins
Re: #467: Expect: 100-continue and "final" status codes Mark Nottingham
Re: #467: Expect: 100-continue and "final" status codes Mark Nottingham
Re: #486: Requiring proxies to process warn-date Mark Nottingham
Re: adding Header Continuation Mark Nottingham

Sunday, 26 May 2013

Saturday, 25 May 2013

Wednesday, 22 May 2013

http2 draft feedback on flow control Patrick McManus
Re: Design Issue: GZIP flag on DATA Frames Roberto Peon
Re: notes on http2 draft Patrick McManus

Tuesday, 21 May 2013

Re: Design Issue: GZIP flag on DATA Frames Patrick McManus
Re: Design Issue: GZIP flag on DATA Frames Frédéric Kayser
Re: Design Issue: GZIP flag on DATA Frames James M Snell
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY James M Snell
Re: Design Issue: GZIP flag on DATA Frames Poul-Henning Kamp
Re: notes on http2 draft Martin Thomson
Re: notes on http2 draft Martin Thomson
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Roberto Peon
Re: Design Issue: GZIP flag on DATA Frames Roberto Peon
Re: Design Issue: GZIP flag on DATA Frames Bjoern Hoehrmann
Re: Design Issue: GZIP flag on DATA Frames James M Snell
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY James M Snell
Re: Design Issue: GZIP flag on DATA Frames Bjoern Hoehrmann
Re: Design Issue: GZIP flag on DATA Frames Poul-Henning Kamp
Re: Design Issue: GZIP flag on DATA Frames Bjoern Hoehrmann
Re: Design Issue: GZIP flag on DATA Frames Bjoern Hoehrmann
Re: Design Issue: GZIP flag on DATA Frames Martin Nilsson
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY 陈智昌
Re: Design Issue: GZIP flag on DATA Frames Poul-Henning Kamp
Re: notes on http2 draft 陈智昌
Re: Design Issue: GZIP flag on DATA Frames Roland Zink
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Patrick McManus
Re: Design Issue: GZIP flag on DATA Frames James M Snell
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY 陈智昌
Re: Design Issue: GZIP flag on DATA Frames Poul-Henning Kamp
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY James M Snell
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY James M Snell
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY 陈智昌
Re: Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY Roberto Peon
Re: Design Issue: GZIP flag on DATA Frames James M Snell
Re: Design Issue: GZIP flag on DATA Frames Poul-Henning Kamp
Design Issue: GZIP flag on DATA Frames James M Snell
Design Issue: Separate HEADERS and PRIORITY Frames, Eliminate HEADERS+PRIORITY James M Snell
Re: notes on http2 draft James M Snell
notes on http2 draft Patrick McManus

Monday, 20 May 2013

Re: "Magic" string Mark Nottingham
Fwd: New Version Notification for draft-snell-httpbis-ext-frames-00.txt James M Snell
Re: adding Header Continuation Roberto Peon
Re: "Magic" string Roberto Peon
Fwd: New Version Notification for draft-snell-httpbis-bohe-08.txt James M Snell
Re: "Magic" string Martin Thomson
Re: adding Header Continuation Martin Thomson
Re: #467: Expect: 100-continue and "final" status codes Alex Rousskov
Re: Preliminary agenda for the SF Interim James M Snell
Re: adding Header Continuation James M Snell
Re: #486: Requiring proxies to process warn-date Alex Rousskov
Preliminary agenda for the SF Interim Mark Nottingham
adding Header Continuation Mark Nottingham
"Magic" string Mark Nottingham
Re: Caching 412 responses Mark Nottingham
Re: #486: Requiring proxies to process warn-date Mark Nottingham

Sunday, 19 May 2013

Re: Lingering Close Roy T. Fielding
Re: p1: handling obs-fold Roy T. Fielding
Re: p1: whitespace in request-target Willy Tarreau
Re: WGLC: SHOULD and conformance Roy T. Fielding
Re: p1: whitespace in request-target Roy T. Fielding
Re: WGLC p1: Tear-down Roy T. Fielding

Friday, 17 May 2013

Re: #467: Expect: 100-continue and "final" status codes Zhong Yu
Re: #467: Expect: 100-continue and "final" status codes Ken Murchison
Re: #467: Expect: 100-continue and "final" status codes Willy Tarreau
Re: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: Upgrade ordering (possible HTTP/2 impact) Peter Occil
Re: Upgrade ordering (possible HTTP/2 impact) Peter Occil
Re: Caching 412 responses Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: #467: Expect: 100-continue and "final" status codes Mark Nottingham
#467: Expect: 100-continue and "final" status codes Mark Nottingham
#486: Requiring proxies to process warn-date Mark Nottingham

Thursday, 16 May 2013

Re: Implementation Notes on Server Push 陈智昌

Wednesday, 15 May 2013

Re: Requiring proxies to process warn-date Alex Rousskov
Re: Implementation Notes on Server Push Patrick McManus
Re: Implementation Notes on Server Push James M Snell
Re: Implementation Notes on Server Push 陈智昌
Re: Implementation Notes on Server Push Patrick McManus
Re: Implementation Notes on Server Push Patrick McManus
Re: Implementation Notes on Server Push 陈智昌
Re: Implementation Notes on Server Push Eliot Lear
Re: Implementation Notes on Server Push Martin Thomson
HTTPBIS WG Interim Meeting, August 5-7, 2013 IESG Secretary
Re: How to pronounce "charset"? Karl Dubost
Re: How to pronounce "charset"? Carsten Bormann
RE: How to pronounce "charset"? Larry Masinter
Part 2: Editorial changes involving "instance of time" Peter Occil
Re: How to pronounce "charset"? Paul Hoffman
Re: Implementation Notes on Server Push James M Snell
Re: p1: Upgrade ordering (possible HTTP/2 impact) Peter Occil
Re: Implementation Notes on Server Push Roberto Peon

Tuesday, 14 May 2013

Re: Implementation Notes on Server Push Martin Thomson
Re: Implementation Notes on Server Push Roberto Peon
Re: Implementation Notes on Server Push 陈智昌
Implementation Notes on Server Push Patrick McManus
Re: Design: Ignored Unknown Frame Types and Intermediaries Roberto Peon
Re: Design: Ignored Unknown Frame Types and Intermediaries James M Snell
Re: Design: Ignored Unknown Frame Types and Intermediaries Yoav Nir
Re: Design: Ignored Unknown Frame Types and Intermediaries Albert Lunde
Re: How to pronounce "charset"? James Cloos
Re: Design: Ignored Unknown Frame Types and Intermediaries Yoav Nir

Monday, 13 May 2013

Re: Design: Ignored Unknown Frame Types and Intermediaries Roberto Peon
Re: Design: Ignored Unknown Frame Types and Intermediaries James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Patrick McManus
Re: Design: Ignored Unknown Frame Types and Intermediaries Roberto Peon
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) 陈智昌
Re: Design: Ignored Unknown Frame Types and Intermediaries James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Martin Thomson
Re: Design: Ignored Unknown Frame Types and Intermediaries Martin Thomson
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Poul-Henning Kamp
Re: How to pronounce "charset"? Roberto Peon
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Poul-Henning Kamp
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Ben Niven-Jenkins
Re: Design: Ignored Unknown Frame Types and Intermediaries Roberto Peon
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) 陈智昌
Re: How to pronounce "charset"? Julian Reschke
Re: How to pronounce "charset"? イアンフェッティ
Re: How to pronounce "charset"? Yoav Nir
Re: How to pronounce "charset"? Tim Bray
Re: How to pronounce "charset"? Carsten Bormann
How to pronounce "charset"? Yi, EungJun
Re: Design: Ignored Unknown Frame Types and Intermediaries James M Snell
Re: Design: Ignored Unknown Frame Types and Intermediaries James M Snell
Re: Design: Ignored Unknown Frame Types and Intermediaries Yoav Nir
Re: http/2 test framework James M Snell
Re: http/2 test framework Mark Nottingham

Sunday, 12 May 2013

Re: #453: Returning the freshest response Mark Nottingham
Re: Associating URI-based identities with HTTP requests Manu Sporny
http/2 test framework 陈智昌
Re: [http-auth] Associating URI-based identities with HTTP requests Manu Sporny
Re: Design: Ignored Unknown Frame Types and Intermediaries Roberto Peon
Re: Design: Ignored Unknown Frame Types and Intermediaries Yoav Nir

Saturday, 11 May 2013

Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Design: Frame type extensibility issues James M Snell
Design: Ignored Unknown Frame Types and Intermediaries James M Snell
Re: Proposal: New Frame Size Text Poul-Henning Kamp
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Roberto Peon
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Martin Thomson
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Roberto Peon
Re: Proposal: New Frame Size Text Martin J. Dürst

Friday, 10 May 2013

Re: Associating URI-based identities with HTTP requests James M Snell
Re: Design Issue: Overlong Frames James M Snell
Re: Design Issue: Overlong Frames Martin Thomson
Re: Design Issue: Overlong Frames James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Poul-Henning Kamp
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Roberto Peon
Re: Design Issue: Overlong Frames James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) 陈智昌
Re: Design Issue: Overlong Frames 陈智昌
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Roberto Peon
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Design Issue: Overlong Frames James M Snell
Re: Design Issue: Overlong Frames James M Snell
Re: Design Issue: Overlong Frames Martin Thomson
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Poul-Henning Kamp
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) 陈智昌
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) 陈智昌
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Martin Thomson
Associating URI-based identities with HTTP requests Manu Sporny
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Martin Thomson
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Martin Thomson
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) 陈智昌
Re: Design Issue: Overlong Frames Martin Thomson
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) Roberto Peon
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Planning for Future Meetings HAYASHI, Tatsuya

Thursday, 9 May 2013

Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell
Re: Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) 陈智昌
Re: 3.5.1 Connection Error Handling James M Snell
Re: 3.5.1 Connection Error Handling Roberto Peon
Design Issue: Overlong Frames James M Snell
Re: Git Issues: PING James M Snell
Re: 3.5.1 Connection Error Handling 陈智昌
Re: 3.5.1 Connection Error Handling Jeff Pinner
3.5.1 Connection Error Handling 陈智昌
Re: p2: section 5.3.2 (Accept header) Mark Nottingham
p2: section 5.3.2 (Accept header) Osama Mazahir
Proposal: New Frame Size Text (was: Re: Design Issue: Frame Size Items) James M Snell

Wednesday, 8 May 2013

Re: redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS Martin Thomson
Re: redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS Martin Thomson
Re: Design Issue: Frame Size Items Poul-Henning Kamp
Re: Design Issue: Frame Size Items James M Snell
Re: http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset 陈智昌
Re: http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset Yoav Nir
redundancy with WINDOW_UPDATE and SETTINGS_FLOW_CONTROL_OPTIONS 陈智昌
http://http2.github.io/http2-spec/#rfc.section.3.1 connections 陈智昌
http://http2.github.io/http2-spec/#FrameHeader section on Flags being unset 陈智昌
Requiring proxies to process warn-date Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: Design Issue: Frame Size Items James M Snell
Re: Design Issue: Frame Size Items Poul-Henning Kamp
Re: p1: Upgrade ordering (possible HTTP/2 impact) Salvatore Loreto
Re: Design Issue: Frame Size Items James M Snell
Re: HTTPBIS WG Interim Meeting, June 13-14, 2013 Mark Nottingham
Re: p1: Via and gateways Mark Nottingham
#443: whitespace in request-target Mark Nottingham
Re: #469: definition of "private" Mark Nottingham
Re: #469: definition of "private" David Morris

Tuesday, 7 May 2013

Re: Design Issue: Frame Size Items 陈智昌
Re: Design Issue: Frame Size Items Martin Thomson
Re: Design Issue: Frame Size Items 陈智昌
Re: Design Issue: Frame Size Items Poul-Henning Kamp
Re: Design Issue: Frame Size Items Roberto Peon
Re: Design Issue: Frame Size Items 陈智昌
Re: Design Issue: Frame Size Items 陈智昌
Re: Design Issue: Frame Size Items James M Snell
Re: #469: definition of "private" Martin Thomson
Re: Design Issue: Frame Size Items James M Snell
Re: #469: definition of "private" David Morris
Re: Design Issue: Frame Size Items Roberto Peon
Re: Design Issue: Frame Size Items Martin Thomson
RE: Design Issue: Frame Size Items Mike Bishop
Re: #469: definition of "private" Martin Thomson
Re: #464, was: p7: editorial suggestions Julian Reschke
Design Issue: Frame Size Items James M Snell
Re: p6: Vary and effects on future requests Mark Nottingham
#453: Returning the freshest response Mark Nottingham
#469: definition of "private" Mark Nottingham
Re: #440: max of max-age Mark Nottingham
Re: #440: max of max-age Bjoern Hoehrmann
Re: p7: forwarding Proxy-* Mark Nottingham
Re: WGLC: SHOULD and conformance Mark Nottingham
Re: p2: Accept-Language missing, empty or no match Mark Nottingham
#440: max of max-age Mark Nottingham
Re: WGLC: p5 MUSTs Mark Nottingham
Re: WGLC: p1 MUSTs Mark Nottingham
Re: WGLC p1: MUST fix Content-Length? Mark Nottingham
Re: WGLC p1: proxy handling of a really bad Content-Length Mark Nottingham
Re: WGLC: p7 MUSTs Mark Nottingham
Fwd: HTTPBIS WG Interim Meeting, June 13-14, 2013 Mark Nottingham

Monday, 6 May 2013

Re: Comments on Explicit/Trusted Proxy Adrien W. de Croy
Re: Comments on Explicit/Trusted Proxy Yoav Nir
Re: Comments on Explicit/Trusted Proxy Adrien W. de Croy
Re: #461, was: p4: editorial suggestions Mark Nottingham
Re: #461, was: p4: editorial suggestions Julian Reschke
Re: #461, was: p4: editorial suggestions Mark Nottingham
Re: #461, was: p4: editorial suggestions Julian Reschke
Re: #461, was: p4: editorial suggestions Mark Nottingham

Sunday, 5 May 2013

Re: Comments on Explicit/Trusted Proxy Yoav Nir
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: Comments on Explicit/Trusted Proxy Werner Baumann

Saturday, 4 May 2013

Re: Comments on Explicit/Trusted Proxy Roberto Peon
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: Comments on Explicit/Trusted Proxy Roberto Peon
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits Roberto Peon
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell

Friday, 3 May 2013

Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type Patrick McManus
Re: Comments on Explicit/Trusted Proxy Adrien W. de Croy
Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits Martin Thomson
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type James M Snell
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type James M Snell
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type Roberto Peon
Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits Roberto Peon
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type 陈智昌
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type James M Snell
Re: Comments on Explicit/Trusted Proxy Roberto Peon
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type 陈智昌
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type James M Snell
Re: Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type Jeff Pinner
Re: Comments on Explicit/Trusted Proxy Adrien W. de Croy
Design Issue: Merge RST_STREAM and GOAWAY into a single ERROR frame type James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits 陈智昌
Re: http/2 initial limits - i see flow control initial limits specified, but not stream limits James M Snell
http/2 initial limits - i see flow control initial limits specified, but not stream limits 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Comments on Explicit/Trusted Proxy Roberto Peon
Re: Comments on Explicit/Trusted Proxy Roberto Peon
Re: Comments on Explicit/Trusted Proxy Roberto Peon
Re: Comments on Explicit/Trusted Proxy Adrien W. de Croy
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: Comments on Explicit/Trusted Proxy Roberto Peon
Re: Comments on Explicit/Trusted Proxy Adrien W. de Croy
Re: Comments on Explicit/Trusted Proxy Roberto Peon

Thursday, 2 May 2013

Design Issue: Can we go ahead and remove persistent settings? James M Snell
Re: Comments on Explicit/Trusted Proxy Benjamin Carlyle
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Comments on Explicit/Trusted Proxy Peter Lepeska
Re: Comments on Explicit/Trusted Proxy Peter Lepeska
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: Comments on Explicit/Trusted Proxy Albert Lunde
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: Comments on Explicit/Trusted Proxy Peter Lepeska
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: Comments on Explicit/Trusted Proxy Peter Lepeska
Re: Comments on Explicit/Trusted Proxy Fabian Keil
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
Re: #461, was: p4: editorial suggestions Julian Reschke
Re: Comments on Explicit/Trusted Proxy Peter Lepeska

Wednesday, 1 May 2013

Re: Design Issue: Life-cycle of a Stream James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
RE: Design Issue: Life-cycle of a Stream Mike Bishop
Re: Design Issue: Life-cycle of a Stream Martin Thomson
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Life-cycle of a Stream 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Design Issue: Life-cycle of a Stream James M Snell
Re: WGLC: p5 MUSTs Alex Rousskov
Re: WGLC: p1 MUST NOT pipeline until connection is persistent Alex Rousskov
Re: WGLC: p5 MUSTs Ken Murchison
Re: WGLC: p1 MUST NOT pipeline until connection is persistent Willy Tarreau
Re: WGLC p1: MUST fix Content-Length? Alex Rousskov
Re: WGLC: p1 MUST NOT pipeline until connection is persistent Alex Rousskov
Re: WGLC p1: proxy handling of a really bad Content-Length Alex Rousskov
Re: WGLC p1: MUST fix Content-Length? Willy Tarreau
Re: WGLC: p1 MUST NOT pipeline until connection is persistent Willy Tarreau
Re: WGLC p1: MUST fix Content-Length? Alex Rousskov
Re: WGLC: p1 MUST NOT pipeline until connection is persistent Alex Rousskov
Re: WGLC p1: proxy handling of a really bad Content-Length Willy Tarreau
Re: WGLC p1: MUST fix Content-Length? Willy Tarreau
Re: p2: Accept-Language missing, empty or no match Willy Tarreau
Re: WGLC: p1 MUST NOT pipeline until connection is persistent Willy Tarreau
WGLC p1: proxy handling of a really bad Content-Length Alex Rousskov
WGLC p1: MUST fix Content-Length? Alex Rousskov
WGLC: p7 MUSTs Alex Rousskov
WGLC: p6 MUSTs Alex Rousskov
WGLC: p5 MUSTs Alex Rousskov
Re: p2: Accept-Language missing, empty or no match Bjoern Hoehrmann
WGLC: p4 MUSTs Alex Rousskov
Re: p2: Accept-Language missing, empty or no match Mark Nottingham

Tuesday, 30 April 2013

Re: #464, was: p7: editorial suggestions Mark Nottingham
Re: #461, was: p4: editorial suggestions Mark Nottingham
Re: WGLC: p1 MUST NOT pipeline until connection is persistent Alex Rousskov
Re: WGLC: p1 MUSTs Willy Tarreau
Re: WGLC: p1 MUSTs Alex Rousskov
Re: WGLC: p1 MUSTs Benjamin Carlyle
WGLC: p2 MUSTs Alex Rousskov
Re: WGLC: p1 MUSTs Willy Tarreau
WGLC: p1 MUSTs Alex Rousskov
Re: HTTPBIS WG Interim Meeting, June 13-14, 2013 Barry Leiba
Re: #461, was: p4: editorial suggestions Julian Reschke
Re: #461, was: p4: editorial suggestions Ken Murchison
Re: WGLC p7: Parsing auth challenges Julian Reschke
Re: WGLC p7: Parsing auth challenges John Sullivan
#461, was: p4: editorial suggestions Julian Reschke
#464, was: p7: editorial suggestions Julian Reschke
Re: WGLC p7: Parsing auth challenges Julian Reschke
Re: p2: Accept-Language missing, empty or no match Bjoern Hoehrmann
Re: WGLC: SHOULD and conformance Mark Nottingham
Re: WGLC: SHOULD and conformance Roy T. Fielding
Re: p7: forwarding Proxy-* Roy T. Fielding
Re: p7: forwarding Proxy-* Mark Nottingham
Re: p7: forwarding Proxy-* Willy Tarreau
Re: WGLC p1: Tear-down Willy Tarreau
Re: WGLC: SHOULD and conformance Willy Tarreau
Re: p1: whitespace in request-target Willy Tarreau
Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
Re: For review: editorial updates pull request James M Snell
Re: WGLC: SHOULD and conformance James M Snell
Re: p2: Accept-Language missing, empty or no match James M Snell
Re: p2: Accept-Language missing, empty or no match Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: p1: whitespace in request-target Mark Nottingham
Re: WGLC p1: Tear-down Adrien W. de Croy
Re: WGLC p1: Tear-down Mark Nottingham
Re: WGLC p1: Tear-down Mark Nottingham
Re: WGLC p1: Delimiting messages with multipart/byteranges Mark Nottingham
Re: WGLC p7: Parsing auth challenges Mark Nottingham
Re: WGLC p1: Tear-down Adrien W. de Croy
WGLC: SHOULD and conformance Mark Nottingham
WGLC: Strengthening SHOULDs Mark Nottingham
Re: p2: deprecating 205 Reset Content? Mark Nottingham
Re: p7: forwarding Proxy-* Mark Nottingham
Re: p7: forwarding Proxy-* Roy T. Fielding
WGLC: misused SHOULDs Mark Nottingham
p7: forwarding Proxy-* Mark Nottingham
Re: Request: Have git commit messages for design changes include links to relevant discussion email threads Mark Nottingham

Monday, 29 April 2013

Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Re: WGLC p1: Delimiting messages with multipart/byteranges Zhong Yu
RE: For review: editorial updates pull request Mike Bishop
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
Re: WGLC p1: Tear-down Zhong Yu
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
Re: WGLC p1: Delimiting messages with multipart/byteranges Zhong Yu
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Roberto Peon
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: WGLC p1: Tear-down Willy Tarreau
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
WGLC p1: Tear-down Ben Niven-Jenkins
WGLC p1: Persistence & 1.1 proxies Ben Niven-Jenkins
WGLC p7: Parsing auth challenges Ben Niven-Jenkins
Re: Request: Have git commit messages for design changes include links to relevant discussion email threads James M Snell
WGLC p1: Delimiting messages with multipart/byteranges Ben Niven-Jenkins
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Request: Have git commit messages for design changes include links to relevant discussion email threads 陈智昌
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams 陈智昌
Re: p2: deprecating 205 Reset Content? James M Snell
Re: p2: deprecating 205 Reset Content? Roy T. Fielding
Re: HTTP/2 and TCP CWND Yuchung Cheng
Re: p2: deprecating 205 Reset Content? Julian Reschke
Re: p2: deprecating 205 Reset Content? 陈智昌
Re: p2: deprecating 205 Reset Content? James M Snell
Re: p6: Vary and effects on future requests Mark Nottingham
Re: WGLC: p4, 304 Not Modified Mark Nottingham
Re: WGLC: p4, 304 Not Modified Ken Murchison
p2 / p6: What is "cacheable"? Mark Nottingham
p2: deprecating 205 Reset Content? Mark Nottingham
p6: Vary and effects on future requests Mark Nottingham
Re: Editorial notes on p6 Mark Nottingham
Re: p7: editorial suggestions Mark Nottingham
Editorial notes on p6 Mark Nottingham

Sunday, 28 April 2013

Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks 陈智昌
Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? 陈智昌
Re: Editorial Issue: Persisted Settings... when does the client need to return them? 陈智昌
Re: p7: editorial suggestions Julian Reschke
#463, was: p7: editorial suggestions Julian Reschke
Re: Editorial Issue: Persisted Settings... when does the client need to return them? James M Snell
Re: Design Issue: PUSH_PROMISE and Stream Priority James M Snell
Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? James M Snell

Saturday, 27 April 2013

Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? Roberto Peon
Re: Design Issue: PUSH_PROMISE and Stream Priority Roberto Peon
Re: Editorial Issue: Persisted Settings... when does the client need to return them? Roberto Peon
Re: Design Issue: PUSH_PROMISE and Stream Priority James M Snell
Re: Design Issue: PUSH_PROMISE and Stream Priority Roberto Peon
Re: Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't? James M Snell
Re: Design Issue: PUSH_PROMISE and Stream Priority James M Snell
Re: Comments on Explicit/Trusted Proxy Yoav Nir
Re: HTTP/2 and TCP CWND Eliot Lear
Re: HTTP/2 and TCP CWND Mark Nottingham
Re: Editorial Issue: Persisted Settings... when does the client need to return them? James M Snell
Re: Editorial Issue: Persisted Settings... when does the client need to return them? Martin Thomson

Friday, 26 April 2013

For review: editorial updates pull request James M Snell
Editorial Issue: Persisted Settings... when does the client need to return them? James M Snell
Re: Editorial Issue: Unknown/Undefined Settings IDs James M Snell
Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? James M Snell
Re: Editorial Issue: Unknown/Undefined Settings IDs Martin Thomson
Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? Martin Thomson
Editorial Issue: Unknown/Undefined Settings IDs James M Snell
Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? James M Snell
Re: Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? Martin Thomson
Design Issue: HEADERS+PRIORITY "MUST be used" for each stream that is created?? James M Snell
Re: Design Issue: PUSH_PROMISE and Stream Priority Roberto Peon
Re: Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't? Martin Thomson
Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks Martin Thomson
Re: Design Issue: PUSH_PROMISE and Stream Priority Martin Thomson
Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks James M Snell
Design Issue: Which frames are allowed to reference Stream ID #0 and which aren't? James M Snell
Re: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks Martin Thomson
RE: Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks Mike Bishop
Design Issue: Unknown Frame Type MUST IGNORE rule and Denial of Service Attacks James M Snell
Re: RST_STREAM and FINAL flag James M Snell
Re: Design Issue: Frame Processing Model James M Snell
Re: Design Issue: PUSH_PROMISE and Stream Priority James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: PUSH_PROMISE and Stream Priority Patrick McManus
Re: Comments on Explicit/Trusted Proxy Peter Lepeska
Re: HTTP/2 and TCP CWND Peter Lepeska
RE: Design Issue: PUSH_PROMISE and Stream Priority RUELLAN Herve
Re: Comments on Explicit/Trusted Proxy Stephen Farrell
RE: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams RUELLAN Herve
RE: Design Issue: PUSH_PROMISE and Stream Priority RUELLAN Herve
Re: Design Issue: PUSH_PROMISE and Stream Priority James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Poul-Henning Kamp
Re: Design Issue: PUSH_PROMISE and Stream Priority 陈智昌
Re: Design Issue: Must Ignore Rule for Unknown Frame Types 陈智昌
Re: Design Issue: PUSH_PROMISE and Stream Priority Roberto Peon
Re: Push Promise Issues 陈智昌
Re: HTTP/2 and TCP CWND 陈智昌
Re: Design Issue: PUSH_PROMISE and Stream Priority Martin Thomson
Re: Design Issue: PUSH_PROMISE and Stream Priority James M Snell
Re: p2: Expectation extensions Bjoern Hoehrmann

Thursday, 25 April 2013

Re: Design Issue: PUSH_PROMISE and Stream Priority Martin Thomson
Re: p2: Expectation extensions Zhong Yu
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: p2: Expectation extensions Bjoern Hoehrmann
Re: Design Issue: Frame Processing Model Martin Thomson
Re: Design Issue: Must Ignore Rule for Unknown Frame Types James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Re: Design Issue: Must Ignore Rule for Unknown Frame Types Martin Thomson
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Design Issue: Must Ignore Rule for Unknown Frame Types James M Snell
Design Issue: Frame Processing Model James M Snell
Comments on Explicit/Trusted Proxy Peter Lepeska
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: RST_STREAM and FINAL flag Martin Thomson
Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams Martin Thomson
Re: RST_STREAM and FINAL flag Jeff Pinner
Re: RST_STREAM and FINAL flag James M Snell
Re: HTTP/2 and TCP CWND Peter Lepeska
RST_STREAM and FINAL flag Martin Thomson
Re: Push Promise Issues Martin Thomson
Design Issue: PUSH_PROMISE and Stream Priority James M Snell
Design Issue: Max Concurrent Streams Limit and Unidirectional Streams James M Snell
Re: HTTP/2 and TCP CWND 陈智昌
Re: HTTP/2 and TCP CWND Peter Lepeska
Re: p2: Considerations for new headers James M Snell
Re: p2: Considerations for new headers Julian Reschke
Re: p2: Purely editorial feedback James Cloos
FYI.. merged pull request.. James M Snell

Wednesday, 24 April 2013

Re: Editorial Issues: Section 4.2.2 Martin Thomson
Editorial Issue: Uniteral Stream Creation James M Snell
Re: HTTP/2 and TCP CWND 陈智昌
Re: p2: Expect: 100-continue and "final" status codes Ken Murchison
Re: Editorial Issues: Section 4.2.2 James M Snell
Re: HTTP/2 and TCP CWND Peter Lepeska
Re: Push Promise Issues James M Snell
Re: Editorial Issues: Section 4.2.2 James M Snell
Re: HTTP Request+Response issues James M Snell
Re: Editorial Issues: Section 4.2.2 Martin Thomson
Re: HTTP Request+Response issues Martin Thomson
Re: p2: Expect: 100-continue and "final" status codes Daniel Stenberg
Re: p2: Expect: 100-continue and "final" status codes Willy Tarreau
Re: p2: Expect: 100-continue and "final" status codes Ken Murchison
Re: Push Promise Issues 陈智昌
Editorial Issues: Section 4.2.2 James M Snell
Re: p2: Expect: 100-continue and "final" status codes Willy Tarreau
Re: p2: Expect: 100-continue and "final" status codes Ken Murchison
HTTP Request+Response issues James M Snell
Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication 陈智昌
Re: HTTP/2 and TCP CWND 陈智昌
Push Promise Issues James M Snell
Re: p2: Expect: 100-continue and "final" status codes Zhong Yu
Re: HTTP/2 and TCP CWND Peter Lepeska
Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication Peter Lepeska
Re: p2: Expect: 100-continue and "final" status codes Amos Jeffries
Re: p2: Expect: 100-continue and "final" status codes Adrien W. de Croy
Re: p2: Considerations for new headers Alexey Melnikov
Re: p2: Considerations for new headers Julian Reschke
p2: Considerations for new headers Mark Nottingham
Re: p2: Expect: 100-continue and "final" status codes Adrien W. de Croy
Re: what's up with commenting on http/2 github issues Mark Nottingham
Re: p1: Via and gateways Willy Tarreau
Re: what's up with commenting on http/2 github issues 陈智昌
Re: p2: Expect: 100-continue and "final" status codes Willy Tarreau
Re: p2: Expect: 100-continue and "final" status codes Willy Tarreau
Re: what's up with commenting on http/2 github issues Julian Reschke
Re: p2: Expect: 100-continue and "final" status codes Amos Jeffries
Re: what's up with commenting on http/2 github issues James M Snell
what's up with commenting on http/2 github issues 陈智昌
Re: p2: Expect: 100-continue and "final" status codes Adrien W. de Croy
Re: p2: Expect: 100-continue and "final" status codes Mark Nottingham
Re: p1: Via and gateways Mark Nottingham
Re: p2: Expect: 100-continue and "final" status codes Amos Jeffries
Re: p2: Expect: 100-continue and "final" status codes Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) 陈智昌

Tuesday, 23 April 2013

Re: p2: scope for status codes Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: p2: Expectation extensions Mark Nottingham
Re: Updated I-D.. James M Snell
Re: p2: Expect: 100-continue and "final" status codes Zhong Yu
Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
Re: p1: Upgrade ordering (possible HTTP/2 impact) 陈智昌
Re: p2: Expect: 100-continue and "final" status codes James M Snell
Re: p2: Expectation extensions James M Snell
Re: p1: Via and gateways Amos Jeffries
Re: p2: Expectation extensions Amos Jeffries
Re: p1: additional security considerations Amos Jeffries
Re: p1: additional security considerations Amos Jeffries
Re: p2: Expect: 100-continue and "final" status codes Ken Murchison
Re: p2: scope for status codes Amos Jeffries
Re: p1: Via and gateways Amos Jeffries
Re: p1: Upgrade ordering (possible HTTP/2 impact) Roberto Peon
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Roberto Peon
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: p1: BWS Mark Nottingham
p2: Expect: 100-continue and "final" status codes Mark Nottingham
p2: Expectation extensions Mark Nottingham
p2: editorial for Expect and 1xx Mark Nottingham
Re: p1: additional security considerations Willy Tarreau
Re: p1: Via and gateways Willy Tarreau
Re: p1: additional security considerations Mark Nottingham
Re: WGLC: p6 editorial nits Mark Nottingham
Re: p1: additional security considerations Willy Tarreau
Re: p1: Via and gateways Mark Nottingham
p1: additional security considerations Mark Nottingham
p1/p2: 203 Non-Authoritative Information Mark Nottingham
Re: p7: editorial suggestions Mark Nottingham
p7: editorial suggestions Mark Nottingham
p5: editorial suggestions Mark Nottingham
p4: editorial suggestions Mark Nottingham
Re: p2: scope for status codes Mark Nottingham

Monday, 22 April 2013

Re: Git Issues: PING Jeff Pinner
Re: Resumable Uploads Ken Murchison
Updated Link I-D James M Snell
Re: Resumable Uploads Carsten Bormann
Re: Resumable Uploads Felix Geisendörfer
Re: Resumable Uploads Julian Reschke
Re: Resumable Uploads Carsten Bormann
Re: Resumable Uploads Felix Geisendörfer
Re: Resumable Uploads Carsten Bormann
Re: p1: HTTP(S) URIs and fragment identifiers Martin J. Dürst

Monday, 15 April 2013

Re: HTTP/2 and TCP CWND Eggert, Lars
Re: HTTP/2 and TCP CWND Eggert, Lars

Friday, 19 April 2013

Re: Resumable Uploads Felix Geisendörfer
Re: Resumable Uploads Felix Geisendörfer

Monday, 22 April 2013

Re: p1: generating "internal" errors Mark Nottingham
Re: p2: Requirements upon proxies for Expect Mark Nottingham
Re: p1: transfer coding registry Mark Nottingham
Re: draft-ietf-httpbis-p2-semantics section 3.1.3.1 confusion Mark Nottingham
Re: p6: Returning the freshest response Mark Nottingham
Re: p2: Content-Length in HEAD responses Mark Nottingham
Re: p1: Purely Editorial Feedback Mark Nottingham
Re: p1: HTTP and TCP name delegation Mark Nottingham
Re: p2: Accept-Language missing, empty or no match Mark Nottingham
Re: p1: Receiving a higher minor HTTP version number Mark Nottingham
Re: p2: Purely editorial feedback Mark Nottingham
Re: p1: HTTP(S) URIs and fragment identifiers Mark Nottingham

Sunday, 21 April 2013

Re: p2: Purely editorial feedback Mark Nottingham
Re: Resumable Uploads Carsten Bormann
Re: Resumable Uploads Felix Geisendörfer
Re: Resumable Uploads Amos Jeffries
Re: p2: Purely editorial feedback Amos Jeffries
Re: p2: scope for status codes Amos Jeffries
Re: Resumable Uploads Mark Nottingham
Re: Resumable Uploads Amos Jeffries
Re: p1: Via and gateways Amos Jeffries
Re: p1: Receiving a higher minor HTTP version number Amos Jeffries

Saturday, 20 April 2013

Re: p2: Content-Length in HEAD responses Mark Nottingham
Re: Git Issues: PING James M Snell
Re: Resumable Uploads Daniel Stenberg
Re: Resumable Uploads Ilari Liusvaara
Re: Git Issues: Reserved Stream-ID Bit 陈智昌
Re: Git Issues: PING 陈智昌
Re: Resumable Uploads Yoav Nir
Git Issues: Reserved Stream-ID Bit James M Snell
Git Issues: PING James M Snell
Re: Updated I-D.. James M Snell
Updated I-D.. James M Snell
Re: p2: Content-Length in HEAD responses Zhong Yu
Re: p1: HTTP(S) URIs and fragment identifiers Zhong Yu
Re: p1: Via and gateways David Morris
Re: p1: Via and gateways Amos Jeffries
Re: p2: Content-Length in HEAD responses Mark Nottingham
Re: p1: handling obs-fold Amos Jeffries
Re: p2: Content-Length in HEAD responses Willy Tarreau
Re: p2: Requirements upon proxies for Expect Willy Tarreau
Re: p1: transfer coding registry Amos Jeffries
p2: scope for status codes Mark Nottingham
Re: p2: Content-Length in HEAD responses Mark Nottingham
Re: p1: Receiving a higher minor HTTP version number Willy Tarreau
Re: p2: Content-Length in HEAD responses Willy Tarreau
p2: Requirements upon proxies for Expect Mark Nottingham
Re: p1: Receiving a higher minor HTTP version number Mark Nottingham
p2: Accept-Language missing, empty or no match Mark Nottingham
p2: Content-Length in HEAD responses Mark Nottingham
Re: Resumable Uploads Felix Geisendörfer
Re: p2: Purely editorial feedback Mark Nottingham
Re: p1: HTTP(S) URIs and fragment identifiers Mark Nottingham
Re: p1: Via and gateways Willy Tarreau
Re: p1: HTTP(S) URIs and fragment identifiers Julian Reschke
Re: p2: Purely editorial feedback Mark Nottingham
Re: p2: Purely editorial feedback Willy Tarreau
Re: p1: Via and gateways Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: p1: handling obs-fold Mark Nottingham
p2: Purely editorial feedback Mark Nottingham
Re: p1: HTTP(S) URIs and fragment identifiers Mark Nottingham
Re: p1: HTTP(S) URIs and fragment identifiers Julian Reschke
Re: p1: Via and gateways Willy Tarreau
Re: p1: Via and gateways David Morris
Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
Re: p1: generating "internal" errors Willy Tarreau
Re: p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
Re: p1: Upgrade ordering (possible HTTP/2 impact) Willy Tarreau
Re: p1: generating "internal" errors Mark Nottingham
Re: p1: generating "internal" errors Willy Tarreau
Re: p1: handling obs-fold Willy Tarreau
Re: p1: Via and gateways Willy Tarreau
Re: p1: Via and gateways Roberto Peon
Re: p1: Receiving a higher minor HTTP version number Willy Tarreau
Re: p1: Via and gateways Mark Nottingham
Re: p1: Receiving a higher minor HTTP version number Mark Nottingham
Re: p1: Receiving a higher minor HTTP version number Willy Tarreau
Re: p1: Via and gateways Willy Tarreau
Re: Resumable Uploads Mark Nottingham
Re: Resumable Uploads Nico Williams
Re: Resumable Uploads Nico Williams
p1: transfer coding registry Mark Nottingham
p1: Upgrade ordering (possible HTTP/2 impact) Mark Nottingham
p1: generating "internal" errors Mark Nottingham
p1: handling obs-fold Mark Nottingham
p1: HTTP and TCP name delegation Mark Nottingham
p1: HTTP(S) URIs and fragment identifiers Mark Nottingham
p1: Receiving a higher minor HTTP version number Mark Nottingham
p1: Via and gateways Mark Nottingham
p1: Purely Editorial Feedback Mark Nottingham

Friday, 19 April 2013

Re: Resumable Uploads Martin Thomson
Re: Resumable Uploads Daniel Stenberg
Re: Resumable Uploads Carsten Bormann
HTTPBIS WG Interim Meeting, June 13-14, 2013 IESG Secretary
Re: Resumable Uploads Martin Thomson
Re: p1: BWS Amos Jeffries
#443: p1: whitespace in request-target Mark Nottingham
Re: p1: BWS Julian Reschke
#442: p1: BWS Mark Nottingham
Re: Resumable Uploads Daniel Stenberg
Re: p1: BWS Mark Nottingham
Re: Resumable Uploads Julian Reschke
Re: p1: BWS Julian Reschke
Re: p1: BWS Roberto Peon
Re: HTTP/2 and TCP CWND Eliot Lear
Re: Resumable Uploads Julian Reschke
Re: p1: BWS Willy Tarreau
Re: HTTP/2 and TCP CWND Wesley Eddy

Thursday, 18 April 2013

Re: HTTP/2 and TCP CWND Nandita Dukkipati
Re: p1: BWS Mark Nottingham
Re: p1: BWS Roberto Peon
Re: Resumable Uploads Albert Lunde
Re: Resumable Uploads Kevin Swiber
Re: Resumable Uploads Daniel Stenberg
Re: Web Keys and HTTP Signatures Manu Sporny
Re: UTF-8 text James Cloos
Re: Web Keys and HTTP Signatures Manu Sporny

Wednesday, 17 April 2013

Re: HTTP/2 and TCP CWND Eggert, Lars

Thursday, 18 April 2013

Resumable Uploads Felix Geisendörfer
Re: Web Keys and HTTP Signatures Manu Sporny
Re: Web Keys and HTTP Signatures Carsten Bormann
Re: Web Keys and HTTP Signatures Manu Sporny
Re: Web Keys and HTTP Signatures Ken Murchison
Re: Web Keys and HTTP Signatures Carsten Bormann
Re: Web Keys and HTTP Signatures David Morris
Re: Web Keys and HTTP Signatures Daniel Friesen
Re: Web Keys and HTTP Signatures Stephen Farrell
Re: Web Keys and HTTP Signatures Amos Jeffries
Re: Web Keys and HTTP Signatures Manu Sporny
Re: p1: BWS Mark Nottingham
Re: Web Keys and HTTP Signatures Carsten Bormann
Re: p1: BWS Julian Reschke
Re: p1: BWS Willy Tarreau
Re: p1: whitespace in request-target Willy Tarreau
Re: Web Keys and HTTP Signatures Carsten Bormann
Re: p1: BWS Amos Jeffries
Re: p1: whitespace in request-target Amos Jeffries
p1: BWS Mark Nottingham
Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? Roberto Peon
p1: whitespace in request-target Mark Nottingham
Re: Web Keys and HTTP Signatures David I. Lehn
Re: Web Keys and HTTP Signatures Martin Thomson

Wednesday, 17 April 2013

RE: Web Keys and HTTP Signatures Manger, James H
RE: 3.3.1 Frame Header: Purpose of 1-bit reserved field? Brian Raymor (MS OPEN TECH)
Re: Web Keys and HTTP Signatures David I. Lehn
Re: HTTP 2.0 "Upgrade" flow Adrien W. de Croy
RE: HTTP 2.0 "Upgrade" flow Gabriel Montenegro
Re: HTTP 2.0 "Upgrade" flow Adrien W. de Croy
Re: HTTP/2 and TCP CWND Yuchung Cheng
Re: HTTP 2.0 "Upgrade" flow Martin Thomson
Re: HTTP 2.0 "Upgrade" flow Adrien W. de Croy
Re: Web Keys and HTTP Signatures Carsten Bormann
Re: HTTP 2.0 "Upgrade" flow Martin Thomson
Re: HTTP 2.0 "Upgrade" flow Adrien W. de Croy
Re: HTTP 2.0 "Upgrade" flow Martin Thomson
Re: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" Martin Thomson
Re: HTTP 2.0 "Upgrade" flow Adrien W. de Croy
Re: Header Serialization Discussion Martin Thomson
RE: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" Gabriel Montenegro
Re: HTTP 2.0 "Upgrade" flow Martin Thomson
Web Keys and HTTP Signatures Manu Sporny
Re: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" Martin Thomson
Re: Status code 451 adoption Julian Reschke
Re: UTF-8 text (was: Header Serialization Discussion) James M Snell
Re: UTF-8 text (was: Header Serialization Discussion) James M Snell
Re: UTF-8 text (was: Header Serialization Discussion) Frédéric Kayser
Re: HTTP/2 and TCP CWND Patrick McManus
Re: Header Serialization Discussion James M Snell
RE: HTTP 2.0 "Upgrade" flow Gabriel Montenegro
Re: HTTP/2 and TCP CWND Wesley Eddy
Re: Header Serialization Discussion Frédéric Kayser
Re: Header Serialization Discussion Frédéric Kayser
Re: HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" Ilari Liusvaara
Re: HTTP 2.0 "Upgrade" flow Mark Nottingham
Re: HTTP 2.0 "Upgrade" flow Roberto Peon
Re: HTTP 2.0 "Upgrade" flow Willy Tarreau
Re: HTTP 2.0 "Upgrade" flow Roberto Peon
Re: HTTP 2.0 "Upgrade" flow Amos Jeffries
Re: HTTP 2.0 "Upgrade" flow Roberto Peon
Re: HTTP 2.0 "Upgrade" flow Adrien W. de Croy
Re: HTTP 2.0 "Upgrade" flow Roberto Peon
Re: HTTP 2.0 "Upgrade" flow Ilya Grigorik
Re: Status code 451 adoption Mark Nottingham
Re: Header Serialization Discussion James M Snell
HTTP/2.0 section 2.4 "Starting HTTP/2.0 with Prior Knowledge" Gabriel Montenegro
Re: HTTP 2.0 "Upgrade" flow Roberto Peon
RE: HTTP 2.0 "Upgrade" flow Gabriel Montenegro
Re: Header Serialization Discussion Martin Nilsson

Tuesday, 16 April 2013

Re: Header Serialization Discussion James M Snell
Re: Header Serialization Discussion Roberto Peon
Re: Quoting email (was: HTTP/2 and TCP CWND) Roberto Peon
Re: Quoting email (was: HTTP/2 and TCP CWND) Roberto Peon
Re: HTTP/2 and TCP CWND Roberto Peon
Re: Header Serialization Discussion James M Snell
Re: Quoting email (was: HTTP/2 and TCP CWND) Simpson, Robby (GE Energy Management)
Re: Quoting email (was: HTTP/2 and TCP CWND) Simpson, Robby (GE Energy Management)
Quoting email (was: HTTP/2 and TCP CWND) Martin Thomson
Re: HTTP/2 and TCP CWND Simpson, Robby (GE Energy Management)
Re: Header Serialization Discussion James M Snell
RE: Header Serialization Discussion RUELLAN Herve
Re: HTTP/2 and TCP CWND Roberto Peon
RE: Header Serialization Discussion RUELLAN Herve
Re: Status code 451 adoption Tim Bray
Re: Status code 451 adoption Tim Bray
Re: HTTP/2 and TCP CWND Simpson, Robby (GE Energy Management)
WGLC: p4, 304 Not Modified Ken Murchison
Re: HTTP/2 and TCP CWND Eliot Lear
Re: Question on Multiplicity of Authorization and WWW-Authenticate Julian Reschke
Re: Question on Multiplicity of Authorization and WWW-Authenticate Julian Reschke
Question on Multiplicity of Authorization and WWW-Authenticate Jan Algermissen
Re: Status code 451 adoption Stephane Bortzmeyer
Re: Status code 451 adoption Mark Nottingham
Re: HTTP/2 and TCP CWND Roberto Peon
Re: Header Serialization Discussion Frédéric Kayser
Re: HTTP/2 and TCP CWND Martin Nilsson
Re: HTTP/2 and TCP CWND Patrick McManus
Re: HTTP/2 and TCP CWND Roberto Peon

Monday, 15 April 2013

Re: Header Serialization Discussion Adrien W. de Croy
Re: Planning for Future Meetings Mark Nottingham
Re: HTTP/2 and TCP CWND Roberto Peon
Re: HTTP/2 and TCP CWND Roberto Peon
RE: HTTP/2 and TCP CWND Gabriel Montenegro
Re: Status code 451 adoption Julian Reschke
Status code 451 adoption Tim Bray
Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? Brian Pane
Re: Planning for Future Meetings James M Snell
Re: Header Serialization Discussion James M Snell
RE: Header Serialization Discussion RUELLAN Herve
Re: HTTP/2 and TCP CWND Roberto Peon
Re: HTTP/2 and TCP CWND Simpson, Robby (GE Energy Management)
Re: FYI: Header Compression Mark Nottingham
Re: FYI: Header Compression James M Snell
Re: Planning for Future Meetings Mark Nottingham
Re: HTTP/2 and TCP CWND Mark Nottingham
FYI: Header Compression Mark Nottingham
Re: HTTP/2 and TCP CWND Eliot Lear

Sunday, 14 April 2013

Re: HTTP 2.0 "Upgrade" flow Ilya Grigorik
Re: HTTP 2.0 "Upgrade" flow Ilari Liusvaara
HTTP 2.0 "Upgrade" flow Ilya Grigorik

Saturday, 13 April 2013

Header Serialization Discussion James M Snell
Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? Roberto Peon
Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? Mark Nottingham
Re: 3.3.1 Frame Header: Purpose of 1-bit reserved field? Adrien W. de Croy
3.3.1 Frame Header: Purpose of 1-bit reserved field? Brian Raymor (MS OPEN TECH)

Friday, 12 April 2013

RE: HTTP/2 and TCP CWND Gabriel Montenegro

Thursday, 11 April 2013

Re: Updated Delta+BOHE Impl in Java James M Snell

Tuesday, 9 April 2013

Re: Updated Delta+BOHE Impl in Java Roberto Peon
Re: WGLC: p5 multiple Range headers Ken Murchison
Re: Updated Delta+BOHE Impl in Java James M Snell
Re: WGLC: p5 multiple Range headers Julian Reschke
Re: Updated Delta+BOHE Impl in Java Martin Thomson
Updated Delta+BOHE Impl in Java James M Snell

Monday, 8 April 2013

Transitioning to TLS Application Layer Protocol Negotiation (ALPN) Brian Raymor (MS OPEN TECH)
RE: HeaderDiff specification RUELLAN Herve

Saturday, 6 April 2013

Re: Compression analysis of perfect atom-based compressor Mark Nottingham

Friday, 5 April 2013

Re: Compression analysis of perfect atom-based compressor Martin Nilsson
RE: Compression analysis of perfect atom-based compressor RUELLAN Herve
Re: Compression analysis of perfect atom-based compressor Roberto Peon
Re: Compression analysis of perfect atom-based compressor Mark Nottingham

Thursday, 4 April 2013

Compression analysis of perfect atom-based compressor Roberto Peon

Wednesday, 3 April 2013

WGLC: p5 multiple Range headers Ken Murchison
Fwd: I-D Action: draft-ietf-httpbis-http2-02.txt Martin Thomson
I-D Action: draft-ietf-httpbis-http2-02.txt internet-drafts@ietf.org
Re: p6: Returning the freshest response Mark Nottingham
Re: p6: Returning the freshest response Amos Jeffries
Re: p6: Returning the freshest response Mark Nottingham

Monday, 1 April 2013

Re: HTTP/2 and TCP CWND Roberto Peon
Re: HTTP/2 and TCP CWND Patrick McManus
Re: HTTP/2 and TCP CWND Robert Collins
Re: HTTP/2 and TCP CWND Roberto Peon
HTTP/2 and TCP CWND Jitu Padhye
Re: p6: Returning the freshest response Martin Thomson
A modest proposal David Kendal
Re: p6: Returning the freshest response Eitan Adler

Last message date: Sunday, 30 June 2013 20:13:58 UTC