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

Thursday, 27 September 2012

Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Mark Nottingham
Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Fall, Kevin

Sunday, 23 September 2012

Re: Content-Length and 304 Amos Jeffries

Saturday, 22 September 2012

Re: Content-Length and 304 Phillip Hallam-Baker
Re: Content-Length and 304 Roy T. Fielding
Re: Content-Length and 304 Zhong Yu
Re: Content-Length and 304 Zhong Yu
Re: Content-Length and 304 Phillip Hallam-Baker
Re: Content-Length and 304 陈智昌
Re: Content-Length and 304 Willy Tarreau
Re: Content-Length and 304 Phillip Hallam-Baker
Re: Content-Length and 304 Willy Tarreau
Re: Content-Length and 304 Tim Bray
Re: Content-Length and 304 Roy T. Fielding
Re: Content-Length and 304 Tim Bray
Re: Content-Length and 304 Roy T. Fielding

Thursday, 20 September 2012

Re: Content-Length and 304 Tim Bray
Re: Content-Length and 304 Mark Nottingham
Re: Content-Length and 304 Julian Reschke
Re: Content-Length and 304 Poul-Henning Kamp
Re: Content-Length and 304 Willy Tarreau
Re: Content-Length and 304 Willy Tarreau
Re: Content-Length and 304 Tim Bray
Re: Content-Length and 304 Zhong Yu
Re: Content-Length and 304 Willy Tarreau
Re: Content-Length and 304 Adrien W. de Croy
Re: Content-Length and 304 Phillip Hallam-Baker
Re: Content-Length and 304 Zhong Yu
Re: Content-Length and 304 Phillip Hallam-Baker
Re: Content-Length and 304 Tim Bray
Re: Content-Length and 304 Phillip Hallam-Baker
Content-Length and 304 Zhong Yu

Wednesday, 19 September 2012

Fwd: [new-work] WG Review: Hypertext Transfer Protocol Bis (httpbis) Mark Nottingham

Tuesday, 18 September 2012

Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Mark Nottingham
Re: Secdir review of draft-ietf-httpbis-p6-cache-20 Mark Nottingham
Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Julian Reschke
Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Fall, Kevin

Monday, 17 September 2012

Referrer - unable to identify the originating page with nested iframes N A Bhaskar

Saturday, 15 September 2012

Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Mark Nottingham
Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Fall, Kevin
Re: question/comment on draft-ietf-httpbis-p5-range-20.txt Mark Nottingham

Friday, 14 September 2012

SPDY compression and CRIME attack Mike Belshe
Re: Semantics of HTTPS Roberto Peon
Re: Semantics of HTTPS Adrien W. de Croy
Re: Semantics of HTTPS Stephen Farrell

Thursday, 13 September 2012

Re: Semantics of HTTPS Adrien W. de Croy
Re: Policy vs. URI (Re: Semantics of HTTPS) Martin Thomson
question/comment on draft-ietf-httpbis-p5-range-20.txt Fall, Kevin
Re: Semantics of HTTPS Carl Wallace
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Poul-Henning Kamp
Re: Semantics of HTTPS Phillip Hallam-Baker
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Phillip Hallam-Baker
Re: Semantics of HTTPS Poul-Henning Kamp
Re: Semantics of HTTPS Carl Wallace
Re: Semantics of HTTPS Phillip Hallam-Baker
Policy vs. URI (Re: Semantics of HTTPS) Carsten Bormann
Re: Semantics of HTTPS Carl Wallace
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Phillip Hallam-Baker
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Karl Dubost
Re: Semantics of HTTPS Martin J. Dürst
Re: Semantics of HTTPS Yoav Nir
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Poul-Henning Kamp
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Mark Nottingham

Thursday, 6 September 2012

Re: Comments on the HTTPbis draft, v20 Poul-Henning Kamp
Re: ABNF for field-value Julian Reschke
#382, was: "OAuth" not listed in initial authentication scheme registry Julian Reschke
"OAuth" not listed in initial authentication scheme registry Evan Prodromou
Re: Managing Obsolete Information Martin J. Dürst
Re: Comments on the HTTPbis draft, v20 Adrien W. de Croy
Re: Comments on the HTTPbis draft, v20 Amos Jeffries

Wednesday, 5 September 2012

Re: Managing Obsolete Information Roy T. Fielding
Re: Comments on the HTTPbis draft, v20 Roy T. Fielding
Re: Managing Obsolete Information Karl Dubost
Re: Managing Obsolete Information Roy T. Fielding
Re: Comments on the HTTPbis draft, v20 Julian Reschke
Re: Managing Obsolete Information Poul-Henning Kamp
Re: Managing Obsolete Information Zhong Yu
RE: Managing Obsolete Information Joe Mason
Comments on the HTTPbis draft, v20 Adrian Custer
Managing Obsolete Information Karl Dubost
Re: Secdir review of draft-ietf-httpbis-p6-cache-20 Mark Nottingham
Re: Secdir review of draft-ietf-httpbis-p6-cache-20 Mark Nottingham
Fwd: Secdir review of draft-ietf-httpbis-p6-cache-20 Mark Nottingham

Sunday, 2 September 2012

ABNF for field-value Adrian Custer

Friday, 31 August 2012

Status of draft-ietf-appsawg-http-forwarded Barry Leiba

Wednesday, 29 August 2012

Re: Status Line Syntax production/parsing Mark Nottingham

Tuesday, 28 August 2012

Re: Status Line Syntax production/parsing Zhong Yu
Re: Status Line Syntax production/parsing Julian Reschke
Re: Status Line Syntax production/parsing Karl Dubost
Re: Status Line Syntax production/parsing Bjoern Hoehrmann
Status Line Syntax production/parsing Karl Dubost

Sunday, 26 August 2012

Re: Semantics of HTTPS Eric Rescorla

Thursday, 23 August 2012

Re: Optimizations vs Functionality vs Architecture Phillip Hallam-Baker
Re: Optimizations vs Functionality vs Architecture Roberto Peon
Re: Optimizations vs Functionality vs Architecture Amos Jeffries

Wednesday, 22 August 2012

Re: Optimizations vs Functionality vs Architecture James M Snell
Re: Optimizations vs Functionality vs Architecture Phillip Hallam-Baker
Re: Optimizations vs Functionality vs Architecture James M Snell
Re: Optimizations vs Functionality vs Architecture Albert Lunde
Re: Optimizations vs Functionality vs Architecture James M Snell
Re: Optimizations vs Functionality vs Architecture Eliot Lear
Re: Optimizations vs Functionality vs Architecture Poul-Henning Kamp
Re: Optimizations vs Functionality vs Architecture Amos Jeffries
Re: Optimizations vs Functionality vs Architecture Amos Jeffries
Re: Optimizations vs Functionality vs Architecture Amos Jeffries
Re: Optimizations vs Functionality vs Architecture James M Snell
Re: Optimizations vs Functionality vs Architecture Amos Jeffries
Re: Optimizations vs Functionality vs Architecture James M Snell

Tuesday, 21 August 2012

Re: Optimizations vs Functionality vs Architecture James M Snell
Re: Optimizations vs Functionality vs Architecture James M Snell
Re: Optimizations vs Functionality vs Architecture Roberto Peon
Re: Optimizations vs Functionality vs Architecture Poul-Henning Kamp
Re: Optimizations vs Functionality vs Architecture Phillip Hallam-Baker
Re: Optimizations vs Functionality vs Architecture Yoav Nir
Re: Optimizations vs Functionality vs Architecture Poul-Henning Kamp
Re: Optimizations vs Functionality vs Architecture Poul-Henning Kamp
Re: HTTP 1.1 --> 2.0 Upgrade James M Snell
Re: Optimizations vs Functionality vs Architecture Phillip Hallam-Baker
Re: HTTP 1.1 --> 2.0 Upgrade Nicolas Mailhot
Re: Optimizations vs Functionality vs Architecture Yoav Nir
Re: Optimizations vs Functionality vs Architecture Poul-Henning Kamp
Re: Optimizations vs Functionality vs Architecture Phillip Hallam-Baker
Re: Optimizations vs Functionality vs Architecture Poul-Henning Kamp
Optimizations vs Functionality vs Architecture Phillip Hallam-Baker
Re: HTTP 1.1 --> 2.0 Upgrade Patrick McManus
Re: HTTP 1.1 --> 2.0 Upgrade Willy Tarreau
Re: HTTP 1.1 --> 2.0 Upgrade Eliot Lear
Re: HTTP 1.1 --> 2.0 Upgrade Roberto Peon
Re: HTTP 1.1 --> 2.0 Upgrade Willy Tarreau
Re: HTTP 1.1 --> 2.0 Upgrade James M Snell
Re: HTTP 1.1 --> 2.0 Upgrade Amos Jeffries

Monday, 20 August 2012

Re: HTTP 1.1 --> 2.0 Upgrade Roberto Peon
Re: HTTP 1.1 --> 2.0 Upgrade Willy Tarreau
Re: HTTP 1.1 --> 2.0 Upgrade Roberto Peon
Re: HTTP 1.1 --> 2.0 Upgrade Roberto Peon
Re: HTTP 1.1 --> 2.0 Upgrade Phillip Hallam-Baker
Re: HTTP 1.1 --> 2.0 Upgrade Ted Hardie
Re: HTTP 1.1 --> 2.0 Upgrade Eliot Lear
Re: HTTP 1.1 --> 2.0 Upgrade Yoav Nir
Re: HTTP 1.1 --> 2.0 Upgrade Patrick McManus
Re: HTTP 1.1 --> 2.0 Upgrade Phillip Hallam-Baker
Re: HTTP 1.1 --> 2.0 Upgrade Eliot Lear
Re: HTTP 1.1 --> 2.0 Upgrade Willy Tarreau
Re: HTTP 1.1 --> 2.0 Upgrade Yoav Nir
Re: HTTP 1.1 --> 2.0 Upgrade Roberto Peon
Re: HTTP 1.1 --> 2.0 Upgrade Phillip Hallam-Baker
Re: HTTP 1.1 --> 2.0 Upgrade Yoav Nir
Re: HTTP 1.1 --> 2.0 Upgrade Willy Tarreau
Re: HTTP 1.1 --> 2.0 Upgrade Willy Tarreau
Re: HTTP 1.1 --> 2.0 Upgrade Yoav Nir
Re: HTTP 1.1 --> 2.0 Upgrade Yoav Nir
Re: HTTP 1.1 --> 2.0 Upgrade Willy Tarreau
Re: HTTP 1.1 --> 2.0 Upgrade Eliot Lear
Re: HTTP 1.1 --> 2.0 Upgrade Julian Reschke
HTTP 1.1 --> 2.0 Upgrade Yoav Nir

Saturday, 18 August 2012

Re: [Editorial Errata Reported] RFC6266 (3325) Mark Nottingham

Friday, 17 August 2012

Thursday, 16 August 2012

Re: In Defense of Header Compresson Ilya Grigorik
RE: In Defense of Header Compresson Henrik Frystyk Nielsen
RE: In Defense of Header Compresson Henrik Frystyk Nielsen
RE: In Defense of Header Compresson Henrik Frystyk Nielsen
Re: In Defense of Header Compresson Phillip Hallam-Baker
Re: In Defense of Header Compresson Phillip Hallam-Baker
Re: In Defense of Header Compresson Roberto Peon
Re: In Defense of Header Compresson David Morris
Re: In Defense of Header Compresson Phillip Hallam-Baker
RE: In Defense of Header Compresson David Morris
RE: In Defense of Header Compresson Robert Brewer
I-D Action: draft-ietf-httpbis-authscheme-registrations-04.txt internet-drafts@ietf.org
RE: In Defense of Header Compresson Patrick McManus
Re: comments on draft-mbelshe-httpbis-spdy-00 Phillip Hallam-Baker
Re: In Defense of Header Compresson Patrick McManus
Re: comments on draft-mbelshe-httpbis-spdy-00 Patrick McManus
Re: comments on draft-mbelshe-httpbis-spdy-00 Eliot Lear
Re: In Defense of Header Compresson Ilya Grigorik
Re: comments on draft-mbelshe-httpbis-spdy-00 陈智昌
RE: HTTP2 Expression of Interest : Squid Paul Leach

Wednesday, 15 August 2012

Re: comments on draft-mbelshe-httpbis-spdy-00 Phillip Hallam-Baker
Re: comments on draft-mbelshe-httpbis-spdy-00 Adrien W. de Croy
Re: comments on draft-mbelshe-httpbis-spdy-00 Adrien W. de Croy
Re: comments on draft-mbelshe-httpbis-spdy-00 Phillip Hallam-Baker
Re: comments on draft-mbelshe-httpbis-spdy-00 Eliot Lear
Re: comments on draft-mbelshe-httpbis-spdy-00 陈智昌
Re: comments on draft-mbelshe-httpbis-spdy-00 Patrick McManus
Re: comments on draft-mbelshe-httpbis-spdy-00 イアンフェッティ
Re: comments on draft-mbelshe-httpbis-spdy-00 Patrick McManus
Re: comments on draft-mbelshe-httpbis-spdy-00 Eliot Lear
Re: comments on draft-mbelshe-httpbis-spdy-00 陈智昌
Re: comments on draft-mbelshe-httpbis-spdy-00 Phillip Hallam-Baker
Re: comments on draft-mbelshe-httpbis-spdy-00 Patrick McManus
RE: In Defense of Header Compresson Henrik Frystyk Nielsen

Tuesday, 14 August 2012

Re: comments on draft-mbelshe-httpbis-spdy-00 Phillip Hallam-Baker
comments on draft-mbelshe-httpbis-spdy-00 Eliot Lear

Saturday, 11 August 2012

New I-D: RESTauth (forget GSS) Nico Williams

Friday, 10 August 2012

Re: FYI... Binary Optimized Header Encoding for SPDY Roberto Peon
Re: Some general SPDY feedback / questions James M Snell
Re: Some general SPDY feedback / questions Adrien W. de Croy

Thursday, 9 August 2012

Re: Some general SPDY feedback / questions James M Snell
Re: Some general SPDY feedback / questions Karl Dubost
Re: Some general SPDY feedback / questions Mike Belshe
Re: Moving forward with HTTP/2.0: proposed charter Salvatore Loreto
Re: Moving forward with HTTP/2.0: proposed charter Amos Jeffries
Re: Moving forward with HTTP/2.0: proposed charter Adrien W. de Croy
Re: Moving forward with HTTP/2.0: proposed charter Amos Jeffries

Wednesday, 8 August 2012

Re: Moving forward with HTTP/2.0: proposed charter David Morris
In Defense of Header Compresson Patrick McManus
Re: Moving forward with HTTP/2.0: proposed charter Salvatore Loreto
Re: Moving forward with HTTP/2.0: proposed charter Salvatore Loreto
Re: Moving forward with HTTP/2.0: proposed charter Salvatore Loreto
Re: Some general SPDY feedback / questions Amos Jeffries
Re: Some general SPDY feedback / questions Adrien W. de Croy
Re: Some general SPDY feedback / questions James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Roberto Peon

Tuesday, 7 August 2012

Re: Some general SPDY feedback / questions Adrien W. de Croy
Re: Some general SPDY feedback / questions James M Snell
Re: Some general SPDY feedback / questions Amos Jeffries
Re: Some general SPDY feedback / questions Mike Belshe
Re: Some general SPDY feedback / questions Adrien W. de Croy
RE: Some general SPDY feedback / questions Henrik Frystyk Nielsen
Re: Some general SPDY feedback / questions Adrien W. de Croy
Re: Some general SPDY feedback / questions James M Snell
Re: Some general SPDY feedback / questions Mark Nottingham
Re: Some general SPDY feedback / questions Poul-Henning Kamp
Re: Some general SPDY feedback / questions Willy Tarreau
RE: Some general SPDY feedback / questions Henrik Frystyk Nielsen
Re: Some general SPDY feedback / questions Mark Nottingham
Re: Some general SPDY feedback / questions Poul-Henning Kamp
Re: Some general SPDY feedback / questions Mark Nottingham
Re: Semantics of HTTPS Poul-Henning Kamp
Re: Semantics of HTTPS Stephen Farrell
Re: Privacy and its costs (was: Re: Mandatory encryption) Greg Wilkins
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Adrien de Croy
Re: Semantics of HTTPS Yoav Nir
Re: Semantics of HTTPS Yoav Nir
Re: Semantics of HTTPS Yoav Nir
Re: Semantics of HTTPS Poul-Henning Kamp
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Poul-Henning Kamp
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Jonathan Ballard
Re: Semantics of HTTPS Amos Jeffries
Re: Semantics of HTTPS Adrien W. de Croy
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS patrick mcmanus
Re: Semantics of HTTPS Amos Jeffries
Re: Semantics of HTTPS Amos Jeffries
Re: Semantics of HTTPS Amos Jeffries

Monday, 6 August 2012

Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Amos Jeffries
Re: FYI... Binary Optimized Header Encoding for SPDY Amos Jeffries
Re: Semantics of HTTPS Adrien W. de Croy
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Adrien W. de Croy
Re: FYI... Binary Optimized Header Encoding for SPDY Amos Jeffries
Re: Semantics of HTTPS Mike Belshe
Re: Semantics of HTTPS Adrien W. de Croy
Re: Semantics of HTTPS 陈智昌
Re: Semantics of HTTPS Adrien W. de Croy
Re: Semantics of HTTPS Jonathan Ballard
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Karl Dubost
Re: Semantics of HTTPS Daniel Stenberg
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Stephen Farrell
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Robert Collins
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Willy Tarreau
Re: Semantics of HTTPS Mark Nottingham
Re: Semantics of HTTPS Willy Tarreau
Semantics of HTTPS Mark Nottingham
Re: Privacy and its costs (was: Re: Mandatory encryption) Mike Belshe
Re: FYI... Binary Optimized Header Encoding for SPDY Martin Nilsson
Discussion of mandatory encryption / privacy impact / etc. Mark Nottingham
Re: Moving forward with HTTP/2.0: proposed charter Mike Belshe
Re: FYI... Binary Optimized Header Encoding for SPDY Jonathan Ballard
Re: Privacy and its costs (was: Re: Mandatory encryption) Mike Belshe
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Zhong Yu
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Roberto Peon
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter Roberto Peon
Re: Privacy and its costs (was: Re: Mandatory encryption) Phillip Hallam-Baker
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter Willy Tarreau
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter Poul-Henning Kamp
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter Robert Collins
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter Poul-Henning Kamp
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter Willy Tarreau
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst
Re: Re[2]: Moving forward with HTTP/2.0: proposed charter Poul-Henning Kamp
Re: Privacy and its costs (was: Re: Mandatory encryption) Tim Bray
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst
Re: Privacy and its costs (was: Re: Mandatory encryption) Greg Wilkins
Re: Privacy and its costs (was: Re: Mandatory encryption) Greg Wilkins
Re: Vancouver minutes (uploaded) Mark Nottingham

Sunday, 5 August 2012

Re: Vancouver minutes (uploaded) Amos Jeffries
Re[2]: FYI... Binary Optimized Header Encoding for SPDY Adrien de Croy
Re[2]: Moving forward with HTTP/2.0: proposed charter Adrien de Croy
Re: FYI... Binary Optimized Header Encoding for SPDY Amos Jeffries
Re: Vancouver minutes (uploaded) Mark Nottingham
Re: FYI... Binary Optimized Header Encoding for SPDY Poul-Henning Kamp
Re: FYI... Binary Optimized Header Encoding for SPDY Phillip Hallam-Baker
Re: FYI... Binary Optimized Header Encoding for SPDY Poul-Henning Kamp
Re: FYI... Binary Optimized Header Encoding for SPDY Amos Jeffries
Re: FYI... In-Stream Key Negotiation Initial Draft Roberto Peon
Re: Moving forward with HTTP/2.0: proposed charter Jonathan Ballard
Re: Moving forward with HTTP/2.0: proposed charter James M Snell
Re: Moving forward with HTTP/2.0: proposed charter Mike Belshe

Saturday, 4 August 2012

RE: Moving forward with HTTP/2.0: proposed charter Henrik Frystyk Nielsen
Re: Moving forward with HTTP/2.0: proposed charter Eliot Lear
Re: Moving forward with HTTP/2.0: proposed charter Julian Reschke
Re: Moving forward with HTTP/2.0: proposed charter Eliot Lear
Re: Moving forward with HTTP/2.0: proposed charter Julian Reschke
Re: Vancouver minutes Zhen Cao

Friday, 3 August 2012

FYI... In-Stream Key Negotiation Initial Draft James M Snell
Re: Moving forward with HTTP/2.0: proposed charter James M Snell
Re: Moving forward with HTTP/2.0: proposed charter Jonathan Ballard
Re: Moving forward with HTTP/2.0: proposed charter Barry Leiba
Re: Moving forward with HTTP/2.0: proposed charter Poul-Henning Kamp
Re[2]: FYI... Binary Optimized Header Encoding for SPDY Adrien de Croy
Re: Moving forward with HTTP/2.0: proposed charter Mark Nottingham
Re[2]: FYI... Binary Optimized Header Encoding for SPDY Adrien de Croy
Re: Moving forward with HTTP/2.0: proposed charter James M Snell
Re: Vancouver minutes Mark Nottingham
Re: Vancouver minutes Willy Tarreau
Moving forward with HTTP/2.0: proposed charter Mark Nottingham
Re: Vancouver minutes Mark Nottingham
Re: FYI... Binary Optimized Header Encoding for SPDY Mike Belshe
Re: Vancouver minutes Yutaka OIWA
Vancouver minutes Mark Nottingham
Re: Would a header/schema compiler help? Roberto Peon
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Roberto Peon
Re: FYI... Binary Optimized Header Encoding for SPDY Mike Belshe
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Zhong Yu
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Jonathan Ballard
Re: FYI... Binary Optimized Header Encoding for SPDY Mike Belshe
Re: FYI... Binary Optimized Header Encoding for SPDY Jonathan Ballard
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst
Re: FYI... Binary Optimized Header Encoding for SPDY Poul-Henning Kamp
Re: FYI... Binary Optimized Header Encoding for SPDY Poul-Henning Kamp
Re: Would a header/schema compiler help? Poul-Henning Kamp
Re: FYI... Binary Optimized Header Encoding for SPDY Adrien W. de Croy
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Martin J. Dürst

Thursday, 2 August 2012

Re: FYI... Binary Optimized Header Encoding for SPDY Martin Nilsson
Re: FYI... Binary Optimized Header Encoding for SPDY Martin Nilsson
Re: Would a header/schema compiler help? Willy Tarreau
Re: Would a header/schema compiler help? Mike Belshe
Re: Would a header/schema compiler help? Phillip Hallam-Baker
Re: Would a header/schema compiler help? David Morris
Re: Would a header/schema compiler help? Daniel Stenberg
Re: Would a header/schema compiler help? Phillip Hallam-Baker
RE: Would a header/schema compiler help? Henrik Frystyk Nielsen
Re: FYI... Binary Optimized Header Encoding for SPDY Yoav Nir
Re: FYI... Binary Optimized Header Encoding for SPDY Eliot Lear
Re: FYI... Binary Optimized Header Encoding for SPDY Timothy Knox
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Yoav Nir
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Eliot Lear
Re: FYI... Binary Optimized Header Encoding for SPDY Martin Thomson
Re: FYI... Binary Optimized Header Encoding for SPDY Mike Belshe
Re: FYI... Binary Optimized Header Encoding for SPDY Eliot Lear
Re: Re[2]: FYI... Binary Optimized Header Encoding for SPDY Poul-Henning Kamp
Re[2]: FYI... Binary Optimized Header Encoding for SPDY Adrien de Croy
Re: FYI... Binary Optimized Header Encoding for SPDY Julian Reschke
Re: FYI... Binary Optimized Header Encoding for SPDY Poul-Henning Kamp
Re: FYI... Binary Optimized Header Encoding for SPDY Mike Belshe
Re: FYI... Binary Optimized Header Encoding for SPDY Poul-Henning Kamp
Re: FYI... Binary Optimized Header Encoding for SPDY James M Snell
Re: FYI... Binary Optimized Header Encoding for SPDY Adrien W. de Croy
Re: FYI... Binary Optimized Header Encoding for SPDY Yoav Nir
Re: FYI... Binary Optimized Header Encoding for SPDY Mike Belshe
Re: FYI... Binary Optimized Header Encoding for SPDY Jonathan Ballard
FYI... Binary Optimized Header Encoding for SPDY James M Snell

Wednesday, 1 August 2012

Re: HTTP 2.0 and a Faster, more Mobile-friendly web Rajeev Bector
Fwd: web+: enabling websites to expose services with custom URI schemes to registerProtocolHandler. Peter Saint-Andre
Re: HTTP/2: Another reason to find a safer encoding Poul-Henning Kamp
Re: HTTP/2: Another reason to find a safer encoding Willy Tarreau
RE: HTTP 2.0 and a Faster, more Mobile-friendly web Benjamin Carlyle
Re: HTTP/2: Another reason to find a safer encoding Zhong Yu

Tuesday, 31 July 2012

Re: Privacy and its costs Eliot Lear
Re: Connection limits, was: Straw-man for our next charter Julian Reschke
Re: HTTP/2: Another reason to find a safer encoding Phillip Hallam-Baker
Re: HTTP/2: Another reason to find a safer encoding James M Snell
RE: HTTP 2.0 and a Faster, more Mobile-friendly web Jitu Padhye
Re: Connection limits, was: Straw-man for our next charter Mike Belshe
Re: HTTP 2.0 and a Faster, more Mobile-friendly web James M Snell
RE: HTTP 2.0 and a Faster, more Mobile-friendly web Jitu Padhye
RE: HTTP 2.0 and a Faster, more Mobile-friendly web Jitu Padhye
HTTP/2: Another reason to find a safer encoding Willy Tarreau
Re: Re[2]: HTTP2 Expression of Interest : Squid Martin Nilsson
Re: Connection limits, was: Straw-man for our next charter Carsten Bormann
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Roberto Peon
Re: Privacy and its costs (was: Re: Mandatory encryption) Yoav Nir
Connection limits, was: Straw-man for our next charter Julian Reschke
Re: Privacy and its costs (was: Re: Mandatory encryption) Tim Bray
Re: Privacy and its costs (was: Re: Mandatory encryption) Yoav Nir
Re: Privacy and its costs (was: Re: Mandatory encryption) Mike Belshe
Re: Re[2]: HTTP2 Expression of Interest : Squid Mike Belshe
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Mike Belshe
Re: Straw-man for our next charter Mike Belshe
RE: HTTP 2.0 and a Faster, more Mobile-friendly web Henrik Frystyk Nielsen

Monday, 30 July 2012

Re[2]: HTTP 2.0 and a Faster, more Mobile-friendly web Adrien W. de Croy
Re: Straw-man for our next charter Jonathan Ballard
Re: Straw-man for our next charter James M Snell
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Jonathan Ballard
RE: HTTP 2.0 and a Faster, more Mobile-friendly web Jitu Padhye
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Martin Nilsson
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Poul-Henning Kamp
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Martin Nilsson
Re: Re[2]: Straw-man for our next charter Adam Barth
Re: HTTP 2.0 and a Faster, more Mobile-friendly web patrick mcmanus
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Yoav Nir
Re: HTTP 2.0 and a Faster, more Mobile-friendly web patrick mcmanus
Re: HTTP 2.0 and a Faster, more Mobile-friendly web patrick mcmanus
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Poul-Henning Kamp
Re: HTTP 2.0 and a Faster, more Mobile-friendly web patrick mcmanus
Re: Straw-man for our next charter Jonathan Ballard
Re: Re[2]: Straw-man for our next charter Larry Masinter
Re: HTTP 2.0 and a Faster, more Mobile-friendly web 陈智昌
Re: Straw-man for our next charter Martin J. Dürst
Re: Re[2]: Straw-man for our next charter Adam Barth
Re: Re[2]: Straw-man for our next charter Poul-Henning Kamp
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Poul-Henning Kamp
RE: HTTP 2.0 and a Faster, more Mobile-friendly web Henrik Frystyk Nielsen
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Figroc Chen
RE: Re[2]: Straw-man for our next charter Larry Masinter
Re: Re[2]: Straw-man for our next charter Adam Barth

Sunday, 29 July 2012

Re: Re[2]: HTTP2 Expression of Interest : Squid Martin Nilsson
Re: Straw-man for our next charter Amos Jeffries
Re[2]: Straw-man for our next charter Adrien W. de Croy
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Amos Jeffries
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Martin Nilsson
Re: HTTP 2.0 and a Faster, more Mobile-friendly web Roberto Peon
HTTP 2.0 and a Faster, more Mobile-friendly web Henrik Frystyk Nielsen
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Larry Masinter
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Larry Masinter
Re: Straw-man for our next charter Larry Masinter
Re: Straw-man for our next charter イアンフェッティ
Re: Straw-man for our next charter Yutaka OIWA
Re: Straw-man for our next charter Adam Barth

Saturday, 28 July 2012

RE: Straw-man for our next charter Larry Masinter
Re: Straw-man for our next charter Amos Jeffries
Re: Straw-man for our next charter Larry Masinter
RE: Straw-man for our next charter Larry Masinter
Re: Thoughts on server push and http/2.0 Roberto Peon

Friday, 27 July 2012

Re: Thoughts on server push and http/2.0 Safruti, Ido
RE: Straw-man for our next charter Rob Trace
Re: Thoughts on server push and http/2.0 Rajeev Bector
Thoughts on server push and http/2.0 Safruti, Ido
Re: RFC6585+HTTP/2.0 := 101 Jonathan Ballard
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Amos Jeffries
Re: RFC6585+HTTP/2.0 := 101 Amos Jeffries
Re: RFC6585+HTTP/2.0 := 101 Mark Nottingham
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Mark Nottingham
Re: Straw-man for our next charter Mark Nottingham
RFC6585+HTTP/2.0 := 101 Jonathan Ballard

Thursday, 26 July 2012

Re: Straw-man for our next charter Ludin, Stephen
Re: Content security model Poul-Henning Kamp
Re: Content security model Mike Belshe
Re: Content security model Phillip Hallam-Baker
Re: Privacy and its costs (was: Re: Mandatory encryption) Martin Thomson
Re: Content security model Martin Thomson
Re: Content security model Phillip Hallam-Baker
Re: Content security model Jonathan Ballard
Re: Content security model Jan Algermissen
Re: #160: Redirects and non-GET methods Julian Reschke
Re: #295: Applying original fragment to "plain" redirected URI (also #43) Julian Reschke
Re: Content security model Poul-Henning Kamp

Wednesday, 25 July 2012

Re: Content security model James French

Thursday, 26 July 2012

Re: Content security model Benjamin Carlyle
Re: Content security model Grahame Grieve
Re: Content security model Mike Belshe
Re: Content security model Poul-Henning Kamp
Re: Privacy and its costs (was: Re: Mandatory encryption) Greg Wilkins
Re: Content security model Phillip Hallam-Baker
Re: Content security model Grahame Grieve
Re: Content security model Phillip Hallam-Baker
Re: Content security model Phillip Hallam-Baker
Re: Content security model Grahame Grieve
Re: Content security model Phillip Hallam-Baker
RE: Content security model Manger, James H

Wednesday, 25 July 2012

Re: Content security model Amos Jeffries
Re: Straw-man for our next charter Eric J. Bowman
Re: REST and HTTP, was: [ietf-http-wg] <none> Eric J. Bowman
Re: Content security model Phillip Hallam-Baker
Re: Content security model Phillip Hallam-Baker
Re: Benjamin Carlyle http 2.0 expression of interest Benjamin Carlyle
Re: Content security model Albert Lunde
Re: Content security model Paul Hoffman
Re: Content security model James M Snell
Content security model Phillip Hallam-Baker
Re: Straw-man for our next charter James M Snell
Re: REST and HTTP, was: [ietf-http-wg] <none> Phillip Hallam-Baker
Re: Straw-man for our next charter Amos Jeffries
Re: Straw-man for our next charter Julian Reschke
REST and HTTP, was: [ietf-http-wg] <none> Julian Reschke
Re: Straw-man for our next charter Poul-Henning Kamp
Straw-man for our next charter Mark Nottingham
RE: Benjamin Carlyle http 2.0 expression of interest Benjamin Carlyle

Tuesday, 24 July 2012

Re: [ietf-http-wg] <none> Eric J. Bowman
Re: Our old friends, weak ETags Eric J. Bowman
Re: Privacy and its costs (was: Re: Mandatory encryption) Dereq Dereq
Explicit Proxies for HTTP/2.0: comments Salvatore Loreto
Re: Our old friends, weak ETags Julian Reschke
Re: Our old friends, weak ETags Amos Jeffries
Re: Our old friends, weak ETags Eric J. Bowman
Re: Benjamin Carlyle http 2.0 expression of interest Amos Jeffries
Issues addressed in the -20 drafts Mark Nottingham

Monday, 23 July 2012

Re: Benjamin Carlyle http 2.0 expression of interest Patrick McManus
Re: Benjamin Carlyle http 2.0 expression of interest 陈智昌
Re: Benjamin Carlyle http 2.0 expression of interest 陈智昌
Re: Benjamin Carlyle http 2.0 expression of interest Amos Jeffries
Re: Benjamin Carlyle http 2.0 expression of interest 陈智昌
Re: Benjamin Carlyle http 2.0 expression of interest Jonathan Ballard
Re: hoba: mixing origin-bound certs and user login Stephen Farrell
hoba: mixing origin-bound certs and user login Manger, James H
Re: Benjamin Carlyle http 2.0 expression of interest Nicolas Mailhot
Re: Benjamin Carlyle http 2.0 expression of interest Stephen Farrell
RE: Benjamin Carlyle http 2.0 expression of interest Nicolas Mailhot
Re: Benjamin Carlyle http 2.0 expression of interest Roberto Peon
RE: Benjamin Carlyle http 2.0 expression of interest Anil Sharma
Re: Discussing Client Sessions Phillip Hallam-Baker
Re: Discussing Client Sessions Mark Nottingham

Sunday, 22 July 2012

Re: Benjamin Carlyle http 2.0 expression of interest Amos Jeffries
Re: Benjamin Carlyle http 2.0 expression of interest Stephen Farrell
Re: Benjamin Carlyle http 2.0 expression of interest Jonathan Ballard
RE: Benjamin Carlyle http 2.0 expression of interest Anil Sharma
Re: Benjamin Carlyle http 2.0 expression of interest Roberto Peon
Re: Benjamin Carlyle http 2.0 expression of interest Roberto Peon
Re: Benjamin Carlyle http 2.0 expression of interest Marcelo Fernandez
Benjamin Carlyle http 2.0 expression of interest Benjamin Carlyle

Saturday, 21 July 2012

Re: More SPDY Related Questions.. Jonathan Ballard
Re: More SPDY Related Questions.. James M Snell
Re: More SPDY Related Questions.. Jonathan Ballard
Re: More SPDY Related Questions.. Roberto Peon
Re: More SPDY Related Questions.. Roberto Peon
Re: More SPDY Related Questions.. James M Snell
More SPDY Related Questions.. James M Snell
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: Discussing Client Sessions Willy Tarreau
Re: Introducing a Session header... Jonathan Ballard
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Zhong Yu
Re: Introducing a Session header... Amos Jeffries
Discussing Client Sessions Mark Nottingham

Friday, 20 July 2012

Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Amos Jeffries
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Amos Jeffries
Re: Privacy and its costs (was: Re: Mandatory encryption) Reto Bachmann-Gmür
Re: Introducing a Session header... Phillip Hallam-Baker
Re: Introducing a Session header... Yoav Nir
Re: Introducing a Session header... Poul-Henning Kamp
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Zhong Yu
Re: Introducing a Session header... Poul-Henning Kamp
Re: Introducing a Session header... Poul-Henning Kamp
Re: Introducing a Session header... Phillip Hallam-Baker
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid James M Snell
Re: Introducing a Session header... James M Snell
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: Introducing a Session header... Willy Tarreau
Re: Introducing a Session header... Phillip Hallam-Baker
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Zhong Yu
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Julian Reschke
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Zhong Yu
Re: Introducing a Session header... James M Snell
Re: Introducing a Session header... Phillip Hallam-Baker
Re: Introducing a Session header... Albert Lunde
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: Introducing a Session header... Willy Tarreau
Re: Introducing a Session header... Poul-Henning Kamp
Re: Introducing a Session header... Roberto Peon
Re: Introducing a Session header... Jonathan Ballard
Re: Introducing a Session header... Poul-Henning Kamp
Re: Cookies, sessions, browser software Jonathan Ballard
Re: Introducing a Session header... James M Snell
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Roberto Peon
Re: Introducing a Session header... James M Snell
Re: Introducing a Session header... Roberto Peon
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid James M Snell
Re: Cookies, sessions, browser software Paul Frazee
Re: Introducing a Session header... Philippe Mougin
Re: Introducing a Session header... Julian Reschke
Re: Cookies, sessions, browser software Ross Nicoll
Re: Introducing a Session header... Ross Nicoll
Re: Introducing a Session header... Poul-Henning Kamp
Cookies, sessions, browser software Paul Frazee
Re: Introducing a Session header... Phillip Hallam-Baker
Re: Introducing a Session header... Jonathan Ballard
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: Introducing a Session header... Willy Tarreau
Re: Introducing a Session header... Poul-Henning Kamp
Re: Introducing a Session header... Ross Nicoll
Re: Introducing a Session header... Poul-Henning Kamp
Fw: Re: Our old friends, weak ETags Adrien de Croy
Re: [ietf-http-wg] <none> Andy Wenk
Re: Introducing a Session header... Nicolas Mailhot
[ietf-http-wg] <none> Samuel Erdtman
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Amos Jeffries
Re: Introducing a Session header... Poul-Henning Kamp
Re: Introducing a Session header... Nicolas Mailhot
Mibiseconds (Re: Our old friends, weak ETags) Carsten Bormann
Re: Introducing a Session header... Amos Jeffries
Re: Our old friends, weak ETags Poul-Henning Kamp
Re: Our old friends, weak ETags Julian Reschke
Re: HTTP without being HTTPS all the time Henry Story
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: HTTP Semantics in HTTP 2.0 Poul-Henning Kamp
Re: Our old friends, weak ETags Carsten Bormann
Re: Our old friends, weak ETags Poul-Henning Kamp
Re: Our old friends, weak ETags Bruce Perens
Re: Discussion of Mandatory TLS in HTTP/2.0 Greg Wilkins
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Amos Jeffries
Re: HTTP without being HTTPS all the time Werner Baumann
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Amos Jeffries
Re: Fwd: Our old friends, weak ETags Poul-Henning Kamp
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: Introducing a Session header... Willy Tarreau
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Amos Jeffries
Re: Introducing a Session header... Amos Jeffries
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: Introducing a Session header... Willy Tarreau
Re: Introducing a Session header... Willy Tarreau
Fwd: Our old friends, weak ETags Mark Nottingham
Re: Our old friends, weak ETags Adrien W. de Croy
Re: Our old friends, weak ETags Adrien W. de Croy
Our old friends, weak ETags Mark Nottingham
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Amos Jeffries
RE: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Osama Mazahir
Re: HTTP without being HTTPS all the time Adam Barth
Re: HTTP Semantics in HTTP 2.0 Mark Nottingham

Thursday, 19 July 2012

Re: Discussion of Mandatory TLS in HTTP/2.0 Mark Nottingham
Re: Introducing a Session header... David Morris
Re: Introducing a Session header... Poul-Henning Kamp
Re: Introducing a Session header... David Morris
Re: Introducing a Session header... Poul-Henning Kamp
Re: Introducing a Session header... David Morris
Re: HTTP without being HTTPS all the time Poul-Henning Kamp
Re: HTTP without being HTTPS all the time Peter Saint-Andre
Re: HTTP without being HTTPS all the time 陈智昌
Re: Introducing a Session header... Willy Tarreau
Re: HTTP without being HTTPS all the time Mike Belshe
Re: Privacy and its costs (was: Re: Mandatory encryption) Grahame Grieve
Re: HTTP without being HTTPS all the time Willy Tarreau
Re: Introducing a Session header... Poul-Henning Kamp
Re: HTTP without being HTTPS all the time Willy Tarreau
Re: HTTP without being HTTPS all the time Poul-Henning Kamp
Re: HTTP without being HTTPS all the time Poul-Henning Kamp
Re: HTTP without being HTTPS all the time Poul-Henning Kamp
Re: HTTP without being HTTPS all the time Phillip Hallam-Baker
HTTP without being HTTPS all the time Nicolas Mailhot
Re: Introducing a Session header... Philippe Mougin
HTTP Semantics in HTTP 2.0 Ted Hardie
Re: HTTP without being HTTPS all the time Willy Tarreau
Opportunity to review and give feedback on IAB privacy document Ted Hardie
Re: Firefox Expression of Interest in HTTP/2.0 陈智昌
HTTP without being HTTPS all the time Mike Belshe
Re: Privacy and its costs (was: Re: Mandatory encryption) Tim Bray
Re: Privacy and its costs (was: Re: Mandatory encryption) Nicolas Mailhot
Re: Discussion of Mandatory TLS in HTTP/2.0 Henry Story
Re: Discussion of Mandatory TLS in HTTP/2.0 Poul-Henning Kamp
Re: Discussion of Mandatory TLS in HTTP/2.0 Stephen Farrell
Re: Discussion of Mandatory TLS in HTTP/2.0 Ross Nicoll
Re: Discussion of Mandatory TLS in HTTP/2.0 Poul-Henning Kamp
Re: Discussion of Mandatory TLS in HTTP/2.0 Stephen Farrell
Re: Discussion of Mandatory TLS in HTTP/2.0 Phillip Hallam-Baker
Re: Privacy and its costs (was: Re: Mandatory encryption) Henry Story
Re: Privacy and its costs (was: Re: Mandatory encryption) Henry Story
Re: Privacy and its costs (was: Re: Mandatory encryption) Karl Dubost
Re: Mandatory encryption Willy Tarreau
RE: Mandatory encryption Anil Sharma
Re: Mandatory encryption Willy Tarreau
Re: Mandatory encryption Poul-Henning Kamp
Re: Mandatory encryption Willy Tarreau
RE: Mandatory encryption Anil Sharma
Re: Mandatory encryption Willy Tarreau
Re: Mandatory encryption Amos Jeffries
Re: Some general SPDY feedback / questions James M Snell
Re: Privacy and its costs (was: Re: Mandatory encryption) Poul-Henning Kamp
RE: Some general SPDY feedback / questions James M Snell
RE: Some general SPDY feedback / questions Manger, James H
Discussion of Mandatory TLS in HTTP/2.0 Mark Nottingham
Re: Privacy and its costs Peter Saint-Andre
Re: Privacy and its costs Nico Williams
Re: Privacy and its costs Peter Saint-Andre
Re: Privacy and its costs (was: Re: Mandatory encryption) Tim Bray
Re: HTTP2 Expression of Interest Amos Jeffries
Re: Mandatory encryption Amos Jeffries
Re: Privacy and its costs (was: Re: Mandatory encryption) Zhong Yu
Re: Explicit Proxy (draft-rpeon-httpbis-exproxy) Chad Goss
Privacy and its costs (was: Re: Mandatory encryption) Martin J. Dürst
Re: Re[2]: Mandatory encryption Zhong Yu
Re: Re[2]: Mandatory encryption Zhong Yu

Wednesday, 18 July 2012

Re: Re[2]: Mandatory encryption Poul-Henning Kamp
Re[2]: [ietf-http-wg] <none> Adrien W. de Croy
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re[2]: Mandatory encryption Adrien W. de Croy
Re: Some general SPDY feedback / questions James M Snell
Re: Mandatory encryption Nicolas Mailhot
Re: Some general SPDY feedback / questions Poul-Henning Kamp
Re: Some general SPDY feedback / questions Roberto Peon
Re: Some general SPDY feedback / questions Roberto Peon
Re: HTTP2 Expression of Interest Werner Baumann
Re: Some general SPDY feedback / questions Poul-Henning Kamp
Some general SPDY feedback / questions James M Snell
Re: p7: rename b64token (to token68) to avoid misunderstandings Yutaka OIWA
Re: p7: rename b64token (to token68) to avoid misunderstandings Julian Reschke
Re: HTTP2 Expression of Interest Poul-Henning Kamp
Re: p7: rename b64token (to token68) to avoid misunderstandings Yutaka OIWA
Re: [ietf-http-wg] <none> Nicolas Mailhot
#376 rename b64token for clarity, was: p7: rename b64token (to token68) to avoid misunderstandings Julian Reschke
Re: HTTP2 Expression of Interest Nicolas Mailhot
Re: [ietf-http-wg] <none> Karl Dubost
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Zhong Yu
HTTP/2.0 negotiation latency Re: Mandatory encryption Brian Pane
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Phillip Hallam-Baker
Re: Mandatory encryption Roberto Peon
Re: Mandatory encryption Roberto Peon
What HTTP/2.0 should mandate instead Phillip Hallam-Baker
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Henry Story
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Zhong Yu
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Henry Story
Re: Protocol Design 101 (Re: Mandatory encryption) Mark Watson
Re: Protocol Design 101 (Re: Mandatory encryption) Carsten Bormann
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Julian Reschke
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Zhong Yu
Re: Protocol Design 101 (Re: Mandatory encryption) Phillip Hallam-Baker
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Henry Story
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Zhong Yu
Re: Mandatory encryption Phillip Hallam-Baker
Re: Mandatory encryption Eliot Lear
Re: Protocol Design 101 (Re: Mandatory encryption) Paul Hoffman
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Zhong Yu
Re: Mandatory encryption Willy Tarreau
Protocol Design 101 (Re: Mandatory encryption) Carsten Bormann
Re: [ietf-http-wg] <none> James M Snell
Re: [ietf-http-wg] <none> Nicolas Mailhot
Re: Mandatory encryption Ross Nicoll
Re: Mandatory encryption Patrick McManus
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames James M Snell
Re: Mandatory encryption Tim Bray
Re: Mandatory encryption Phillip Hallam-Baker
Re: [ietf-http-wg] <none> Tim Bray
Re: HTTP2 Expression of Interest Yoav Nir
Re: Mandatory encryption Eliot Lear
[ietf-http-wg] <none> Nicolas Mailhot
Re: Mandatory encryption Phillip Hallam-Baker
Re: Re[6]: HTTP2 Expression of Interest Nicolas Mailhot
Re: Mandatory encryption Patrick McManus
Re: Mandatory encryption Patrick McManus
Re: Mandatory encryption Patrick McManus
Re: Mandatory encryption Patrick McManus
Re: Re[6]: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea Phillip Hallam-Baker
RE: Minimizing/avoiding User-Agent, was: SPDY Header Frames Anil Sharma
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Amos Jeffries
Re: Mandatory encryption Phillip Hallam-Baker
Re: p7: rename b64token (to token68) to avoid misunderstandings Alexey Melnikov
Re: #375: Most Conservative (caching and date parsing) Amos Jeffries
Re: p7: rename b64token (to token68) to avoid misunderstandings Amos Jeffries
Re: HTTP2 Expression of Interest Poul-Henning Kamp
Re[2]: HTTP2 Expression of Interest Adrien de Croy
Re[2]: HTTP2 Expression of Interest Adrien de Croy
Re: HTTP2 Expression of Interest Mike Belshe
RE: HTTP2 Expression of Interest Henrik Frystyk Nielsen
Re: Introducing a Session header... Poul-Henning Kamp
Re: Re[6]: HTTP2 Expression of Interest Willy Tarreau
Re[8]: HTTP2 Expression of Interest Adrien de Croy
Re: HTTP2 Expression of Interest Julian Reschke
Re: Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea Poul-Henning Kamp
Re: #375: Most Conservative (caching and date parsing) Julian Reschke
Re: Re[6]: HTTP2 Expression of Interest Mike Belshe
Re: Mandatory encryption J Ross Nicoll
Re: p7: rename b64token (to token68) to avoid misunderstandings Julian Reschke
Re: Mandatory encryption Yoav Nir
p7: rename b64token (to token68) to avoid misunderstandings Manger, James H
Re: Re[6]: HTTP2 Expression of Interest Willy Tarreau
Re: Mandatory encryption Willy Tarreau
Re: Re[6]: HTTP2 Expression of Interest Mike Belshe
Re: Mandatory encryption Mike Belshe
Re: Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea Mike Belshe
Re: Re[2]: Some reasons why mandating use ofSSL for HTTP is a really bad idea James M Snell
Re: Re[6]: HTTP2 Expression of Interest Willy Tarreau
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea James M Snell
Re: Mandatory encryption Willy Tarreau
Re: Mandatory encryption prerequisites Eliot Lear
Re: Re[4]: HTTP2 Expression of Interest Roberto Peon
Re[4]: Some reasons why mandating use ofSSL for HTTP is a really bad idea Adrien W. de Croy
Re: Mandatory encryption Mark Watson
Re: Mandatory encryption Mike Belshe
Re: Re[6]: HTTP2 Expression of Interest Mike Belshe
Re: Re[2]: Some reasons why mandating use ofSSL for HTTP is a really bad idea Mike Belshe
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: Re[6]: HTTP2 Expression of Interest Phillip Hallam-Baker
Re[2]: Some reasons why mandating use ofSSL for HTTP is a really bad idea Adrien W. de Croy
Re: Mandatory encryption Phillip Hallam-Baker
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Mike Belshe
Re: HTTP2 Expression of Interest Mike Belshe
Re: Re[6]: HTTP2 Expression of Interest Mike Belshe
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: Re[6]: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Mike Belshe
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Grahame Grieve
Re: HTTP2 Expression of Interest Mike Belshe
Re: Some reasons why mandating use ofSSL for HTTP is a really bad idea Mike Belshe
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: Re[6]: HTTP2 Expression of Interest Mike Belshe
Re: Mandatory encryption Mike Belshe
Re[6]: HTTP2 Expression of Interest Adrien W. de Croy
Re: HTTP2 Expression of Interest Mike Belshe
Re: Re[4]: HTTP2 Expression of Interest Mike Belshe
Re[4]: HTTP2 Expression of Interest Adrien W. de Croy
Re: Mandatory encryption Phillip Hallam-Baker
Re: Re[2]: HTTP2 Expression of Interest Rajeev Bector
Some reasons why mandating use ofSSL for HTTP is a really bad idea Adrien W. de Croy
Re[2]: HTTP2 Expression of Interest Adrien W. de Croy
Re: HTTP2 Expression of Interest Martin Thomson
Re: HTTP2 Expression of Interest Martin J. Dürst
Re: Mandatory encryption Mike Belshe
Re[2]: HTTP2 Expression of Interest Adrien W. de Croy
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Martin J. Dürst
Re: Mandatory encryption Phillip Hallam-Baker
Re: Introducing a Session header... Martin J. Dürst
Re: Introducing a Session header... Martin J. Dürst
Re: #375: Most Conservative (caching and date parsing) Mark Nottingham
Re: Mandatory encryption Grahame Grieve
Re: Introducing a Session header... Phillip Hallam-Baker
Mandatory encryption Paul Hoffman
Re: Introducing a Session header... Amos Jeffries
Re: Introducing a Session header... Mark Nottingham
Re: Introducing a Session header... James M Snell
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Mark Nottingham
Re: HTTP2 Expression of Interest : Squid James M Snell
Re: Introducing a Session header... Mark Nottingham
RE: HTTP2 Expression of Interest : Squid Paul Leach
Re: Introducing a Session header... James M Snell

Tuesday, 17 July 2012

Re: Introducing a Session header... Martin Thomson
Fwd: Introducing a Session header... James M Snell
Re: Introducing a Session header... Dirk Pranke
Re: HTTP2 Expression of Interest Mike Belshe
Re: Introducing a Session header... イアンフェッティ
Re: Introducing a Session header... Martin Thomson
Re: Introducing a Session header... Ross Nicoll
Re: HTTP2 Expression of Interest James M Snell
Introducing a Session header... James M Snell
Re: HTTP2 Expression of Interest Grahame Grieve
RE: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Osama Mazahir
Re: HTTP2 Expression of Interest Tim Bray
RE: HTTP2 Expression of Interest Doug Beaver
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames James M Snell
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Poul-Henning Kamp
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Karl Dubost
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Roberto Peon
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Poul-Henning Kamp
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames James M Snell
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Julian Reschke
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Karl Dubost
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: usability of 100-continue, was: HTTP2 Expression of Interest : Squid Roberto Peon
Re: HTTP2 Expression of Interest : Squid Roberto Peon
Re: HTTP2 Expression of Interest : Squid Roberto Peon
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Julian Reschke
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Nicolas Mailhot
usability of 100-continue, was: HTTP2 Expression of Interest : Squid Julian Reschke
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Karl Dubost
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Poul-Henning Kamp
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Karl Dubost
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Poul-Henning Kamp
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Roland Zink
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Karl Dubost
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames James M Snell
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Poul-Henning Kamp
RE: HTTP2 Expression of Interest : Squid Osama Mazahir
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Nicolas Mailhot
Re: Minimizing/avoiding User-Agent, was: SPDY Header Frames Nicolas Mailhot
Re: character encoding in header fields, was: SPDY Header Frames Nicolas Mailhot
Minimizing/avoiding User-Agent, was: SPDY Header Frames Julian Reschke
Re: SPDY Header Frames Nicolas Mailhot
Re: HTTP2 Expression of Interest : Squid James M Snell
Re: HTTP2 Expression of Interest : Squid Julian Reschke
RE: Re[4]: HTTP2 Expression of Interest : Squid Gabriel Montenegro
Re: SPDY Header Frames James M Snell
RE: Re[2]: HTTP2 Expression of Interest : Squid Gabriel Montenegro
Re: character encoding in header fields, was: SPDY Header Frames Julian Reschke
Re: SPDY Header Frames Patrick McManus
Re: character encoding in header fields, was: SPDY Header Frames James M Snell
RE: character encoding in header fields, was: SPDY Header Frames Robert Brewer
Re: character encoding in header fields, was: SPDY Header Frames Poul-Henning Kamp
Re: character encoding in header fields, was: SPDY Header Frames James M Snell
Re: character encoding in header fields, was: SPDY Header Frames Julian Reschke
Re: character encoding in header fields, was: SPDY Header Frames James M Snell
Re: SPDY Header Frames James M Snell
Would a header/schema compiler help? Phillip Hallam-Baker
Re: SPDY Header Frames Julian Reschke
Re: SPDY Header Frames Phillip Hallam-Baker
Re: SPDY Header Frames Poul-Henning Kamp
Re: SPDY Header Frames Roberto Peon
Re: Re[4]: HTTP2 Expression of Interest : Squid Poul-Henning Kamp
Re[4]: HTTP2 Expression of Interest : Squid Adrien de Croy
Re: Re[2]: HTTP2 Expression of Interest : Squid Poul-Henning Kamp
Re[2]: HTTP2 Expression of Interest : Squid Adrien de Croy
Re: HTTP2 Expression of Interest : Squid Amos Jeffries
Re: character encoding in header fields, was: SPDY Header Frames Amos Jeffries
Re: HTTP2 Expression of Interest : Squid Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: SPDY Header Frames Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
character encoding in header fields, was: SPDY Header Frames Julian Reschke
Re: Response to HTTP2 expresions of interest Martin J. Dürst
Re: SPDY Header Frames Poul-Henning Kamp
Re: SPDY Header Frames Roberto Peon
Re: SPDY Header Frames Poul-Henning Kamp
Re: SPDY Header Frames Julian Reschke
Re: HTTP/2 Expression of luke-warm interest: Varnish Roberto Peon
Fwd: SPDY Feedback Mark Nottingham
Re: SPDY Header Frames Martin J. Dürst
Re: SPDY Header Frames James M Snell
Re: SPDY Header Frames Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Yoav Nir
Re: SPDY Header Frames James M Snell
Re: SPDY Header Frames James M Snell
Re: SPDY Header Frames Mike Belshe
Re: HTTP/2 Expression of luke-warm interest: Varnish Mike Belshe
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: SPDY Header Frames James M Snell
Re: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: HTTP/2 Expression of luke-warm interest: Varnish Brian Pane
Re: HTTP2 Expression of Interest : Squid Poul-Henning Kamp
Re: #375: Most Conservative (caching and date parsing) Poul-Henning Kamp
Re: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: #375: Most Conservative (caching and date parsing) Julian Reschke
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Mike Belshe
Re: #375: Most Conservative (caching and date parsing) Mark Nottingham

Monday, 16 July 2012

Re: Implementing SPDY, is a day a meaningful criteria? Mark Nottingham
Re: HTTP/2 Expression of luke-warm interest: Varnish Willy Tarreau
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
New version of draft-farrell-httpbis-hoba Paul Hoffman
Re: HTTP/2 Expression of luke-warm interest: Varnish Willy Tarreau
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Roberto Peon
Re: Re[2]: HTTP2 Expression of Interest : Squid Roberto Peon
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: Re[2]: HTTP2 Expression of Interest : Squid Poul-Henning Kamp
httpbis -20 drafts Julian Reschke
I-D Action: draft-ietf-httpbis-method-registrations-09.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p7-auth-20.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p6-cache-20.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p5-range-20.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p4-conditional-20.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p3-payload-20.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p2-semantics-20.txt internet-drafts@ietf.org
I-D Action: draft-ietf-httpbis-p1-messaging-20.txt internet-drafts@ietf.org
Re: Re[2]: HTTP2 Expression of Interest : Squid Mike Belshe
Re: HTTP/2 Expression of luke-warm interest: Varnish Roberto Peon
Re: Implementing SPDY, is a day a meaningful criteria? Phillip Hallam-Baker
Re: Re[2]: HTTP2 Expression of Interest : Squid Roberto Peon
Re: #375: Most Conservative (caching and date parsing) Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Subbu Allamaraju
Re: #375: Most Conservative (caching and date parsing) Yutaka OIWA
Re: Re[2]: HTTP2 Expression of Interest : Squid Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Mike Belshe
Re: #375: Most Conservative (caching and date parsing) Poul-Henning Kamp
Re: Re[2]: HTTP2 Expression of Interest : Squid Mike Belshe
Re: Implementing SPDY, is a day a meaningful criteria? Poul-Henning Kamp
Re: HTTP2 Expression of Interest : Squid Patrick McManus
Re: #375: Most Conservative (caching and date parsing) Yutaka OIWA
Implementing SPDY, is a day a meaningful criteria? Phillip Hallam-Baker
Re: HTTP/2 Expression of luke-warm interest: Varnish Patrick McManus
Re: HTTP/2 Expression of luke-warm interest: Varnish Patrick McManus
Re: HTTP2 Expression of Interest : Squid Patrick McManus
Re[2]: HTTP/2 Expression of luke-warm interest: Varnish Adrien de Croy
Re: HTTP/2 Expression of luke-warm interest: Varnish Phillip Hallam-Baker
Re[2]: HTTP2 Expression of Interest : Squid Adrien de Croy
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: #365: Conditional Request Security Considerations Mark Nottingham
Re: HTTP/2 Expression of luke-warm interest: Varnish Mark Nottingham
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: HTTP/2 Expression of luke-warm interest: Varnish Yoav Nir
Re: HTTP/2 Expression of luke-warm interest: Varnish Yoav Nir
Re: HTTP/2 Expression of luke-warm interest: Varnish Yoav Nir
Re: #375: Most Conservative (caching and date parsing) Amos Jeffries
Re: HTTP/2 Expression of luke-warm interest: Varnish Mark Nottingham
Re: HTTP/2 Expression of luke-warm interest: Varnish HAYASHI, Tatsuya
Re: HTTP/2 Expression of luke-warm interest: Varnish James M Snell
Fwd: HTTP/2 Expression of luke-warm interest: Varnish Grahame Grieve
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: HTTP2 Expression of Interest : Squid Roberto Peon
Re: HTTP2 Expression of Interest : Squid Mike Belshe
Re: HTTP2 Expression of Interest : Squid James M Snell
#375: Most Conservative (caching and date parsing) Mark Nottingham
Re: HTTP2 Expression of Interest : Squid Mike Belshe
#365: Conditional Request Security Considerations Mark Nottingham
Re: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: HTTP2 Expression of Interest : Squid Mike Belshe
Re: #350: WGLC Issue for p4: Optionality of Conditional Request Support Mark Nottingham
HTTP/2.0 Expression of Interest: Akamai Ludin, Stephen
Re: HTTP2 Expression of Interest : Squid Willy Tarreau
HTTP/2 expression of interest: F5 Jeroen de Borst
HTTP2 Expression of Interest James Tucker
Re: SPDY Header Frames Amos Jeffries
Fwd: HTTP/2.0 proposal feedback Mark Nottingham
Re: HTTP/2 Expression of luke-warm interest: Varnish Mark Nottingham
Re: SPDY Header Frames James M Snell
Re: SPDY Header Frames HAYASHI, Tatsuya
Re: HTTP2 Expression of Interest : Squid Jonathan Ballard

Sunday, 15 July 2012

Re: HTTP2 Expression of Interest : Squid Mike Belshe
Re: HTTP2 Expression of Interest : Squid Roberto Peon
Re: HTTP2 Expression of Interest : Squid Amos Jeffries
HTTP2 Expression of Interest Sam Johnston
Reminder about Opera and SPDY, HTTP/2.0 Karl Dubost
Re: HTTP2 Expression of Interest : Squid Willy Tarreau
Re: Response to HTTP2 expresions of interest Albert Lunde
Re: HTTP2 Expression of Interest : Squid Roberto Peon
HTTP2 Expression of Interest: Alibaba Joshua Zhu
Re: HTTP2 Expression of Interest Poul-Henning Kamp
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: HTTP2 Expression of Interest Poul-Henning Kamp
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: HTTP2 Expression of Interest : Squid Julian Reschke
Re: HTTP2 Expression of Interest : Squid tom
Re: HTTP2 Expression of Interest : Squid tom
HTTP2 Expression of Interest : Squid Amos Jeffries
Re: SPDY Header Frames Amos Jeffries
Re: SPDY Header Frames Amos Jeffries
Re: Response to HTTP2 expresions of interest Julian Reschke
Re: HTTP2 Expression of Interest James M Snell
Re: SPDY Header Frames Poul-Henning Kamp
Re: SPDY Header Frames Amos Jeffries
Re: HTTP2 Expression of Interest Willy Tarreau
HTTP2 Expression of Interest Doug Beaver
Fwd: HTTP2 Expression of Interest [twitter] Mark Nottingham

Saturday, 14 July 2012

Re: Response to HTTP2 expresions of interest HAYASHI, Tatsuya
Re: SPDY Header Frames HAYASHI, Tatsuya
Re: Response to HTTP2 expresions of interest Mike Belshe
Re: Response to HTTP2 expresions of interest Phillip Hallam-Baker
Re: SPDY Header Frames Roberto Peon
Re: SPDY Header Frames Roland Zink
Re: SPDY Header Frames Willy Tarreau
Re: SPDY Header Frames HAYASHI, Tatsuya
Re: Response to HTTP2 expresions of interest HAYASHI, Tatsuya
Re: draft-montenegro-httpbis-multilegged-auth-01 Yutaka OIWA
HTTP2 Expression of Interest Jonathan Silvera
Re: SPDY Header Frames Poul-Henning Kamp
Re: SPDY Header Frames Roberto Peon
Re: SPDY Header Frames Poul-Henning Kamp
Re: SPDY Header Frames Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest Willy Tarreau
Re: SPDY Header Frames Willy Tarreau
Re: SPDY Header Frames Willy Tarreau
Re: Response to HTTP2 expresions of interest Tim Bray
Re: SPDY Header Frames Jonathan Ballard

Friday, 13 July 2012

Re: SPDY Header Frames Roland Zink
Re: SPDY Header Frames Jonathan Ballard
Re: SPDY Header Frames Mike Belshe
Re: Response to HTTP2 expresions of interest Stephen Farrell
Re: SPDY Header Frames Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: SPDY Header Frames Willy Tarreau
Re: Response to HTTP2 expresions of interest Stephen Farrell
Re: HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest Nico Williams
Expression of Interest in HTTP/2.0 Roberto Peon
Re: SPDY Header Frames Poul-Henning Kamp
SPDY Header Frames James M Snell
Re: Misconceptions about the GSS-API Nico Williams
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: Misconceptions about the GSS-API Nico Williams
Re: HTTP/2 Expression of luke-warm interest: Varnish Julian Reschke
Re: KEY_NEGO within SPDY (was: Re: Response to HTTP2 expresions of interest) James M Snell
Re: Misconceptions about the GSS-API Nico Williams
KEY_NEGO within SPDY (was: Re: Response to HTTP2 expresions of interest) James M Snell
Re: Misconceptions about the GSS-API Phillip Hallam-Baker
Re: Misconceptions about the GSS-API Poul-Henning Kamp
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: Misconceptions about the GSS-API Nico Williams
Re: Misconceptions about the GSS-API Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest HAYASHI, Tatsuya
Misconceptions about the GSS-API Nico Williams
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
RE: HTTP2 Expression of Interest Paul Leach
Re: HTTP2 Expression of Interest Nico Williams
Re: Response to HTTP2 expresions of interest Brian Pane
Re: draft-montenegro-httpbis-multilegged-auth-01 Alexey Melnikov
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest James M Snell
Number of round trips in draft-melnikov-httpbis-scram-auth-00 Alexey Melnikov
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest James M Snell
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: Response to HTTP2 expresions of interest Willy Tarreau
Re: Response to HTTP2 expresions of interest Phillip Hallam-Baker
Re: Response to HTTP2 expresions of interest Tim Bray
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: Response to HTTP2 expresions of interest Poul-Henning Kamp
Re: HTTP2 Expression of Interest Nico Williams
Response to HTTP2 expresions of interest Phillip Hallam-Baker
Re: Explicit Proxy (draft-rpeon-httpbis-exproxy) Roberto Peon
Explicit Proxy (draft-rpeon-httpbis-exproxy) Chad Goss
Re: HTTP2 Expression of Interest: curl Yutaka OIWA
HTTP2 Expression of Interest : haproxy Willy Tarreau
Re: HTTP2 Expression of Interest: curl Stephen Farrell
Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt Wendy Seltzer
Re: #241: clarify eval order/interaction of conditional headers Roy T. Fielding
Re: HTTP2 Expression of Interest Phillip Hallam-Baker
Re: HTTP2 Expression of Interest Nico Williams
HTTP2 Expression of Interest Paul Hoffman

Thursday, 12 July 2012

HTTP/2 Expression of luke-warm interest: Varnish Poul-Henning Kamp
Re: #241: clarify eval order/interaction of conditional headers Eric J. Bowman
Re: MACing HTTP requests/responses (Re: Content-Integrity header) Ludin, Stephen
HTTP2 Expression of Interest: curl Daniel Stenberg
Re: #241: clarify eval order/interaction of conditional headers Julian Reschke
Re: #241: clarify eval order/interaction of conditional headers Roy T. Fielding
Re: MACing HTTP requests/responses (Re: Content-Integrity header) James M Snell
Re: MACing HTTP requests/responses (Re: Content-Integrity header) Phillip Hallam-Baker
Re: MACing HTTP requests/responses (Re: Content-Integrity header) Julian Reschke
Re: MACing HTTP requests/responses (Re: Content-Integrity header) James M Snell
Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt Phillip Hallam-Baker
Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt Tim Bray
Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt Wendy Seltzer
Re: MACing HTTP requests/responses (Re: Content-Integrity header) Phillip Hallam-Baker
Re: MACing HTTP requests/responses (Re: Content-Integrity header) James M Snell
HTTP2 Expression of Interest Rob Trace
Firefox Expression of Interest in HTTP/2.0 Patrick McManus
Re: #372: refactor conditional header field descriptions Julian Reschke
Re: #364 Capturing more information in the method registry Julian Reschke
Re: #372: refactor conditional header field descriptions Willy Tarreau
Re: #241: clarify eval order/interaction of conditional headers Julian Reschke
Re: #371: If-Modified-Since lacks definition for method != GET Julian Reschke
Re: #372: refactor conditional header field descriptions Julian Reschke
Re: #372: refactor conditional header field descriptions Mark Nottingham
Re: #371: If-Modified-Since lacks definition for method != GET Mark Nottingham
Re: Using HTTP Trailers [was: Content-Integrity header] Zhong Yu
Re: Using HTTP Trailers [was: Content-Integrity header] Amos Jeffries
Re: MACing HTTP requests/responses (Re: Content-Integrity header) Phillip Hallam-Baker
Re: Using HTTP Trailers [was: Content-Integrity header] Zhong Yu
Re: Using HTTP Trailers [was: Content-Integrity header] Amos Jeffries

Wednesday, 11 July 2012

Re: MACing HTTP requests/responses (Re: Content-Integrity header) James M Snell
Re: MACing HTTP requests/responses (Re: Content-Integrity header) Nico Williams
Re: MACing HTTP requests/responses (Re: Content-Integrity header) Phillip Hallam-Baker
Re: Content-Integrity header Nico Williams
Re: Using HTTP Trailers [was: Content-Integrity header] Phillip Hallam-Baker
Re: Content-Integrity header Phillip Hallam-Baker
Re: Using HTTP Trailers [was: Content-Integrity header] Zhong Yu
Re: Content-Integrity header Nico Williams
Re: Content-Integrity header Ludin, Stephen
Re: Using HTTP Trailers [was: Content-Integrity header] Ludin, Stephen
RE: draft-montenegro-httpbis-multilegged-auth-01 Jonathan Silvera
RE: draft-montenegro-httpbis-multilegged-auth-01 Jonathan Silvera
MACing HTTP requests/responses (Re: Content-Integrity header) Nico Williams
Re: Using HTTP Trailers [was: Content-Integrity header] Zhong Yu
Re: Content-Integrity header Phillip Hallam-Baker
Re: 451 Unavailable For Legal Reasons Karl Dubost
#371: If-Modified-Since lacks definition for method != GET Julian Reschke
Re: #370: If-None-Match vs 412 vs ignoring the header field Julian Reschke
Re: If-* vs Range (part of #366) Yves Lafon
Re: #370: If-None-Match vs 412 vs ignoring the header field Yves Lafon
Re: Using HTTP Trailers [was: Content-Integrity header] Wenbo Zhu
Re: Using HTTP Trailers [was: Content-Integrity header] Zhong Yu
Re: Associated resource for PUT Julian Reschke
Re: Content-Integrity header Yutaka OIWA
Feedback on REST-GSS Nico Williams
Re: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt James M Snell
Re: Using HTTP Trailers [was: Content-Integrity header] James M Snell
Re: Using HTTP Trailers [was: Content-Integrity header] Brian Pane
Re: Using HTTP Trailers [was: Content-Integrity header] James M Snell

Tuesday, 10 July 2012

Using HTTP Trailers [was: Content-Integrity header] Mark Nottingham
RE: Associated resource for PUT Robert Brewer
Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-01.txt Tim Bray
RE: Associated resource for PUT Amos Jeffries
#372: refactor conditional header field descriptions Julian Reschke
#370: If-None-Match vs 412 vs ignoring the header field Julian Reschke
Re: Content-Integrity header Phillip Hallam-Baker
Re: Content-Integrity header Ludin, Stephen
Re: draft-montenegro-httpbis-multilegged-auth-01 Nico Williams
RE: Associated resource for PUT Robert Brewer
Re: draft-montenegro-httpbis-multilegged-auth-01 Alexey Melnikov
Re: Associated resource for PUT Julian Reschke
Associated resource for PUT Robert Brewer
RE: Status code for censorship? Dereq Dereq
Re: Status code for censorship? Dereq Dereq
Re: Status code for censorship? Dereq Dereq
Re: Status code for censorship? Dereq Dereq
RE: draft-montenegro-httpbis-multilegged-auth-01 Amos Jeffries
Re: draft-montenegro-httpbis-multilegged-auth-01 Mark Nottingham
Caching unsafe methods - p6 overview clarification Mark Nottingham

Monday, 9 July 2012

FYI: p6 re-org Mark Nottingham
Re: Content-Integrity header Amos Jeffries
RE: draft-montenegro-httpbis-multilegged-auth-01 Jonathan Silvera
Re: Content-Integrity header HAYASHI, Tatsuya
Re: draft-montenegro-httpbis-multilegged-auth-01 Alexey Melnikov
Re: draft-montenegro-httpbis-multilegged-auth-01 Yutaka OIWA

Sunday, 8 July 2012

Re: draft-montenegro-httpbis-multilegged-auth-01 Nico Williams
draft-montenegro-httpbis-multilegged-auth-01 Alexey Melnikov

Saturday, 7 July 2012

Re: Content-Integrity header Phillip Hallam-Baker
Re: Content-Integrity header Martin Thomson

Friday, 6 July 2012

Re: Content-Integrity header James M Snell
Re: Content-Integrity header Phillip Hallam-Baker
Re: Content-Integrity header Phillip Hallam-Baker
Re: Content-Integrity header Phillip Hallam-Baker
Re: Content-Integrity header Roy T. Fielding
Re: Content-Integrity header Poul-Henning Kamp
Re: Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 Julian Reschke
Content-Integrity header Phillip Hallam-Baker
If-* vs Range (part of #366) Julian Reschke
Re: WGLC #353: Multiple Values in Cache-Control headers Julian Reschke
Re: #364 Capturing more information in the method registry Julian Reschke
Re: #364 Capturing more information in the method registry Amos Jeffries

Thursday, 5 July 2012

Re: draft-ietf-appsawg-http-forwarded-05 issue: multiple copies of Forwarded vs comma-separated list Barry Leiba
Re: draft-ietf-appsawg-http-forwarded-05 issue: multiple copies of Forwarded vs comma-separated list Roy T. Fielding
Re: #364 Capturing more information in the method registry Julian Reschke
Re: #364 Capturing more information in the method registry Julian Reschke
Re: #364 Capturing more information in the method registry Julian Reschke
Re: WGLC #353: Multiple Values in Cache-Control headers Julian Reschke
Re: WGLC #353: Multiple Values in Cache-Control headers Julian Reschke
Re: Revision of p2 2.2.1 / who can generate a status code? Mark Nottingham
Re: #364 Capturing more information in the method registry Julian Reschke
Re: #350: WGLC Issue for p4: Optionality of Conditional Request Support Mark Nottingham
Re: #364 Capturing more information in the method registry Mark Nottingham
Re: #364 Capturing more information in the method registry Mark Nottingham

Wednesday, 4 July 2012

Re: #241: clarify eval order/interaction of conditional headers Mark Nottingham
Re: WGLC #353: Multiple Values in Cache-Control headers Mark Nottingham
Re: #241: clarify eval order/interaction of conditional headers Zhong Yu
Re: WGLC #353: Multiple Values in Cache-Control headers Julian Reschke
Re: #359 clarify connection header field values are case-insensitive Amos Jeffries
Re: Revision of p2 2.2.1 / who can generate a status code? Amos Jeffries
Re: Revision of p2 2.2.1 / who can generate a status code? Amos Jeffries
Re: Revision of p2 2.2.1 / who can generate a status code? Amos Jeffries
Straw-man agenda for Vancouver sessions Mark Nottingham

Tuesday, 3 July 2012

Re: #364 Capturing more information in the method registry Mark Nottingham
Re: #364 Capturing more information in the method registry Amos Jeffries
Re: [httpbis] #364: Capturing more information in the method registry mike amundsen
Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes Mark Nottingham
RE: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes Gabriel Montenegro
RE: [httpbis] #364: Capturing more information in the method registry Musatov, Martin - CW
Re: [httpbis] #364: Capturing more information in the method registry Julian Reschke
Re: [httpbis] #364: Capturing more information in the method registry mike amundsen
Re: [httpbis] #364: Capturing more information in the method registry Mark Nottingham
Re: [httpbis] #364: Capturing more information in the method registry mike amundsen
Re: [httpbis] #364: Capturing more information in the method registry Mark Nottingham
Re: [httpbis] #364: Capturing more information in the method registry mike amundsen
Re: [httpbis] #364: Capturing more information in the method registry Mark Nottingham
Re: Revision of p2 2.2.1 / who can generate a status code? Mark Nottingham
Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes Roberto Peon
Re: #271: use of "may" and "should" Mark Nottingham
draft-ietf-appsawg-http-forwarded-05 issue: multiple copies of Forwarded vs comma-separated list Barry Leiba
Re: #359 clarify connection header field values are case-insensitive Willy Tarreau
Re: #271: use of "may" and "should" Julian Reschke
Re: #271: use of "may" and "should" Julian Reschke
Re: #271: use of "may" and "should" Julian Reschke
Re: Revision of p2 2.2.1 / who can generate a status code? John Sullivan
Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes Julian Reschke
Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes Jan Engelhardt
Expression of Interest from Jetty. Greg Wilkins
Re: #359 clarify connection header field values are case-insensitive Julian Reschke
Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes Stephen Farrell
Re: #359 clarify connection header field values are case-insensitive Mark Nottingham
#359 clarify connection header field values are case-insensitive Julian Reschke
Re: [httpbis] #364: Capturing more information in the method registry Jan Algermissen
Re: [httpbis] #364: Capturing more information in the method registry Jan Algermissen
#241: clarify eval order/interaction of conditional headers Mark Nottingham
#364 Capturing more information in the method registry Julian Reschke
Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt Erlend Hamnaberg
Re: cache invalidation and "denial of service" [was: WGLC #363: rare cases] Julian Reschke
Fwd: [httpbis] #364: Capturing more information in the method registry Mark Nottingham
#360: Considerations for new cache directives Mark Nottingham
Re: WGLC #353: Multiple Values in Cache-Control headers Mark Nottingham
Re: WGLC #363: rare cases Mark Nottingham
Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt mike amundsen
Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt Amos Jeffries
cache invalidation and "denial of service" [was: WGLC #363: rare cases] Mark Nottingham
Re: Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes Mark Nottingham
Revision of p2 2.2.1 / who can generate a status code? Mark Nottingham
Re: #271: use of "may" and "should" Mark Nottingham
Re: #271: use of "may" and "should" Amos Jeffries
Fwd: New Version Notification for draft-nottingham-link-template-00.txt Mark Nottingham

Monday, 2 July 2012

Vancouver Scheduling Mark Nottingham

Friday, 29 June 2012

Re: #271: use of "may" and "should" James French

Monday, 2 July 2012

Re: I-D Action: draft-ietf-httpbis-method-registrations-08.txt Julian Reschke
I-D Action: draft-ietf-httpbis-method-registrations-08.txt internet-drafts@ietf.org

Last message date: Thursday, 27 September 2012 17:06:37 UTC