ietf-http-wg@w3.org from April to June 2012 by author

Adrien de Croy

• Re: options or protocols? (Thursday, 5 April)
• Re: options or protocols? (Thursday, 5 April)

Adrien W. de Croy

• Re: Review of draft-ietf-httpbis-p7-auth-19.txt (Tuesday, 8 May)
• Re: Some proxy needs (Tuesday, 10 April)
• Re[2]: Some proxy needs (Sunday, 8 April)
• Re[4]: multiplexing -- don't do it (Saturday, 7 April)
• Re[2]: multiplexing -- don't do it (Saturday, 7 April)
• Re[2]: multiplexing -- don't do it (Saturday, 7 April)
• Re: options or protocols? (Thursday, 5 April)
• Re: options or protocols? (Thursday, 5 April)
• Re: Backwards compatibility (Wednesday, 4 April)
• Re[2]: multiplexing -- don't do it (Wednesday, 4 April)
• Re[2]: multiplexing -- don't do it (Tuesday, 3 April)
• Re[2]: multiplexing -- don't do it (Tuesday, 3 April)
• Re[2]: breaking TLS (Was: Re: multiplexing -- don't do it) (Tuesday, 3 April)
• Re[3]: multiplexing -- don't do it (Monday, 2 April)
• Re[2]: multiplexing -- don't do it (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re[4]: multiplexing -- don't do it (Sunday, 1 April)
• Re[2]: multiplexing -- don't do it (Sunday, 1 April)
• Re: Make HTTP 2.0 message/transport format agnostic (Sunday, 1 April)

Albert Lunde

• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• "SAML V2.0 Metadata Extensions for Login and Discovery User Interface" (Thursday, 3 May)

Alek Storm

• Re: Proposal for cache control of pushed streams (Thursday, 7 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Proposal for cache control of pushed streams (Thursday, 7 June)
• Re: SPDY Review (Thursday, 7 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)

Alexandre Morgaut

• Re: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)

Alexey Melnikov

• Re: WGLC #357: Authentication Exchanges (Friday, 29 June)
• Fwd: Status of draft-ietf-appsawg-http-forwarded-04.txt (Wednesday, 27 June)
• Fwd: I-D Action: draft-melnikov-httpbis-scram-auth-00.txt (Monday, 11 June)
• Comments on draft-oiwa-httpbis-auth-extension-00 (Sunday, 10 June)
• Fwd: Last Call: RFC 2818 (HTTP Over TLS) to Proposed Standard (Friday, 1 June)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• Re: WGLC #349: "strength" (Thursday, 31 May)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• Belated WGLC review of p6 (caching) (Wednesday, 9 May)
• Review of draft-ietf-httpbis-p5-range-19.txt (Tuesday, 8 May)
• Review of draft-ietf-httpbis-p7-auth-19.txt (Tuesday, 8 May)
• Review of draft-ietf-httpbis-p4-conditional-19.txt (Monday, 16 April)

Amos Jeffries

• Re: WGLC #363: rare cases (Wednesday, 27 June)
• Re: WGLC #357: Authentication Exchanges (Thursday, 21 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: Fwd: Proposing Status Codes (Tuesday, 12 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Tuesday, 12 June)
• Re: Proposing Status Codes (Tuesday, 12 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Monday, 11 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 8 June)
• Re: WGLC #348: Realms and scope (Thursday, 7 June)
• Re: [httpauth] Mutual authentication proposal (Tuesday, 5 June)
• Re: WGLC #349: "strength" (Saturday, 2 June)
• Re: add GETAJAX verb/method in http protocol (Thursday, 24 May)
• Re: Review of draft-ietf-httpbis-p5-range-19.txt (Wednesday, 9 May)
• Re: Review of draft-ietf-httpbis-p7-auth-19.txt (Tuesday, 8 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Sunday, 6 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Sunday, 6 May)
• Re: Fwd: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 6 ABNF (Wednesday, 2 May)
• Re: Fwd: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.2 (Wednesday, 2 May)
• Re: Fwd: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Wednesday, 2 May)
• Re: Fwd: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Wednesday, 2 May)
• Re: Comments/Issues on P1 (Tuesday, 24 April)
• Re: Comments/Issues on P1 (Tuesday, 24 April)
• Re: Last-Modified header in 304 and 206 responses (Saturday, 14 April)
• Re: Last-Modified header in 304 and 206 responses (Friday, 13 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 13 April)
• Re: Portal authorization (Friday, 13 April)
• Re: multiplexing -- don't do it (Friday, 13 April)
• Re: Backwards compatibility (Tuesday, 3 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Tuesday, 3 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: multiplexing -- don't do it (Sunday, 1 April)

Andreas Maier

• HTTP status code for "response too large" (Wednesday, 18 April)

Andreas Petersson

• Re: [apps-discuss] WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Monday, 14 May)
• Re: [apps-discuss] WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Monday, 14 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Monday, 14 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Friday, 4 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 6 ABNF (Friday, 4 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Friday, 4 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.2 (Friday, 4 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Friday, 4 May)

Anthony Bryan

• Re: Some proxy needs (Wednesday, 18 April)

Ben Niven-Jenkins

• Re: Comments/Issues on P1 (Tuesday, 24 April)
• Comments/Issues on P1 (Monday, 23 April)
• WGLC issue: P6 - Multiple values in Cache-Control headers (Monday, 23 April)
• WGLC issue: P4 - ETags & conditional requests (Monday, 23 April)
• Re: Proposal to make draft-kucherawy-httpbis-summary a WG document (Monday, 2 April)

Bjoern Hoehrmann

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Monday, 25 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Sunday, 24 June)
• Re: #271: use of "may" and "should" (Sunday, 24 June)
• Re: #307 (untangle Cache-Control ABNF) (Tuesday, 19 June)
• Re: #307 (untangle Cache-Control ABNF) (Tuesday, 19 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• Re: WGLC #349: "strength" (Monday, 4 June)
• Re: part 2, 5.1 "the response payload is a representation of the target resource" (Wednesday, 23 May)

Brian Pane

• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)

Carsten Bormann

• Re: enc: URL scheme (Thursday, 14 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: 2.0 and Radio Impacts/battery efficiency (Saturday, 14 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)

Christian RIGONI

• add GETAJAX verb/method in http protocol (Tuesday, 22 May)

Christopher Müller

• AW: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)

Cullen Jennings

• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)

Cyrus Daboo

• Re: HTTP status code for "response too large" (Wednesday, 18 April)
• Re: HTTP status code for "response too large" (Wednesday, 18 April)

Dang Thi Thu van

• [ietf-http-wg] <none> (Thursday, 24 May)
• 404 Not Found (Tuesday, 22 May)
• MIT PGP Key Server -- Email Help (Tuesday, 22 May)
• IETF (Thursday, 5 April)

Dang Van

• ietf-http-wg@w3.org (Thursday, 28 June)
• Dang Van a annulé l'événement « Webinar: Agile: Kanban or Scrum? When to Use Which and How to Get the Best of Both ». (Wednesday, 27 June)
• Vous êtes invité à l’événement « Webinar: Agile: Kanban or Scrum? When to Use Which and How to Get the Best of Both ». (Wednesday, 27 June)

Daniel Stenberg

• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• proxy config (was Re: multiplexing -- don't do it) (Tuesday, 3 April)

David Morris

• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Sunday, 10 June)
• Re: WGLC #348: Realms and scope (Wednesday, 6 June)
• Re: WGLC #348: Realms and scope (Tuesday, 5 June)
• Re: WGLC #349: "strength" (Monday, 4 June)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• Re: WGLC #349: "strength" (Thursday, 31 May)
• Re: multiplexing -- don't do it (Saturday, 7 April)
• Re: HTTP -> Messages -> Transport factoring (Friday, 6 April)

Dereq Dereq

• Re: 451 Unavailable For Legal Reasons (Monday, 25 June)

Dirk Pranke

• Re: FYI: CORS Last Call (Friday, 6 April)

Eliot Lear

• Re: Some proxy needs (Monday, 9 April)
• options or protocols? (Thursday, 5 April)

Eric Lawrence

• RE: proxy config (was Re: multiplexing -- don't do it) (Tuesday, 3 April)

Gabriel Montenegro

• RE: New Version Notification for draft-montenegro-httpbis-speed-mobility-02.txt (Monday, 25 June)
• RE: New Version Notification for draft-montenegro-httpbis-speed-mobility-02.txt (Saturday, 23 June)
• Some thoughts on server push and client pull (Thursday, 7 June)

Gordon P. Hemsley

• Accept-Language language tag order (Saturday, 28 April)

Henrik Frystyk Nielsen

• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Monday, 25 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Monday, 25 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• RE: multiplexing -- don't do it (Friday, 6 April)
• RE: HTTP -> Messages -> Transport factoring (Thursday, 5 April)

Henry Story

• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Tuesday, 3 April)

Herbert van de Sompel

• New version of Memento I-D (Thursday, 24 May)

IESG Secretary

• CORRECTION: WG Action: RECHARTER: Hypertext Transfer Protocol Bis (httpbis) (Thursday, 26 April)

J Ross Nicoll

• Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: Status code for censorship? (Sunday, 10 June)
• Re: add GETAJAX verb/method in http protocol (Tuesday, 22 May)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: multiplexing -- don't do it (Monday, 2 April)

Jack Bates

• Re: Forward proxies and CDN/mirrors (Thursday, 14 June)
• Forward proxies and CDN/mirrors (Saturday, 19 May)

Jacob Appelbaum

• 451 Unavailable For Legal Reasons (Wednesday, 13 June)

James French

• Re: WGLC #349: "strength" (Thursday, 31 May)

James M Snell

• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Tuesday, 12 June)
• Re: Proposing Status Codes (Tuesday, 12 June)
• Fwd: Proposing Status Codes (Tuesday, 12 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Sunday, 10 June)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Saturday, 28 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: FYI: CORS Last Call (Friday, 6 April)

Jamie Lokier

• Re: multiplexing -- don't do it (Monday, 9 April)
• Re: multiplexing -- don't do it (Saturday, 7 April)
• Re: multiplexing -- don't do it (Saturday, 7 April)

Jan Algermissen

• Re: HTTP status code for "response too large" (Wednesday, 18 April)
• Re: HTTP status code for "response too large" (Wednesday, 18 April)

John Sullivan

• Re: WGLC #363: rare cases (Wednesday, 27 June)
• Re: WGLC #363: rare cases (Tuesday, 26 June)
• Re: WGLC #354 - ETags & conditional requests (Friday, 22 June)
• Re: WGLC #354 - ETags & conditional requests (Thursday, 21 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Tuesday, 12 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Tuesday, 15 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Monday, 14 May)

Jon Leighton

• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)

Jonathan Silvera

• Multi-legged Authentication for HTTP Multiplexing (Monday, 18 June)

Julian Reschke

• Re: WGLC #354 - ETags & conditional requests (Wednesday, 27 June)
• Re: Advice to define where new status codes can be generated (Tuesday, 26 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 25 June)
• Re: Advice to define where new status codes can be generated (Monday, 25 June)
• Re: #307 (untangle Cache-Control ABNF) (Sunday, 24 June)
• #271: use of "may" and "should" (Sunday, 24 June)
• Re: #271: SHOULD review in p7 (Sunday, 24 June)
• Re: #271: SHOULD review in p4 (Saturday, 23 June)
• Re: #271: SHOULD review in p5 (Saturday, 23 June)
• Re: #271: SHOULD review in p7 (Saturday, 23 June)
• may/should (Friday, 22 June)
• Re: #347: clarify that 201 can imply *multiple* resources were created (Thursday, 21 June)
• Re: #361: ABNF requirements for recipients [was: #307 untangle Cache-Control ABNF] (Thursday, 21 June)
• Re: #347: clarify that 201 can imply *multiple* resources were created (Thursday, 21 June)
• Re: WGLC #357: Authentication Exchanges (Thursday, 21 June)
• Re: #347: clarify that 201 can imply *multiple* resources were created (Thursday, 21 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: #361: ABNF requirements for recipients [was: #307 untangle Cache-Control ABNF] (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• #361: ABNF requirements for recipients [was: #307 untangle Cache-Control ABNF] (Tuesday, 19 June)
• Re: #307 (untangle Cache-Control ABNF) (Tuesday, 19 June)
• Re: #307 (untangle Cache-Control ABNF) (Sunday, 17 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)
• Re: inv-maxage Cache-Control directive syntax, was: Fwd: I-D Action: draft-nottingham-linked-cache-inv-00.txt (Friday, 15 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• inv-maxage Cache-Control directive syntax, was: Fwd: I-D Action: draft-nottingham-linked-cache-inv-00.txt (Thursday, 14 June)
• Re: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• #360 (advice on defining new cache directives), was: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• Re: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• Re: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• Re: #307 (untangle Cache-Control ABNF) (Wednesday, 13 June)
• Re: #307 (untangle Cache-Control ABNF) (Wednesday, 13 June)
• Re: #307 (untangle Cache-Control ABNF) (Tuesday, 12 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Tuesday, 12 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Monday, 11 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Monday, 11 June)
• #307 (untangle Cache-Control ABNF) (Sunday, 10 June)
• Re: #346: Registry policies (Sunday, 10 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 8 June)
• Re: #346: Registry policies (Friday, 8 June)
• Re: #247: "intended usage" in our registries (Friday, 8 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 8 June)
• Re: httpbis-method-registrations (Thursday, 7 June)
• Re: httpbis-method-registrations (Thursday, 7 June)
• Re: SPDY Review (Thursday, 7 June)
• Re: WGLC #348: Realms and scope (Thursday, 7 June)
• Re: WGLC #348: Realms and scope (Tuesday, 5 June)
• Re: WGLC #349: "strength" (Tuesday, 5 June)
• Re: #295: Applying original fragment to "plain" redirected URI (also #43) (Monday, 4 June)
• Re: #160: Redirects and non-GET methods (Monday, 4 June)
• Re: WGLC issue: following HTTP redirects (Monday, 4 June)
• Re: Accept-Language language tag order (Monday, 4 June)
• Re: Accept-Language language tag order (Monday, 4 June)
• Re: Accept-Language language tag order (Monday, 4 June)
• Re: FYI: LCI -02 (Monday, 4 June)
• Re: FYI: LCI -02 (Saturday, 2 June)
• Re: WGLC #349: "strength" (Saturday, 2 June)
• Re: WGLC #349: "strength" (Saturday, 2 June)
• Terminology: "credentials" (Saturday, 2 June)
• Re: WGLC #348: Realms and scope (Saturday, 2 June)
• Re: WGLC issue: following HTTP redirects (Saturday, 2 June)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• Re: WGLC #349: "strength" (Thursday, 31 May)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• Re: WGLC #349: "strength" (Thursday, 31 May)
• Re: part 2, 5.1 "the response payload is a representation of the target resource" (Wednesday, 23 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Monday, 14 May)
• Fwd: I-D Action: draft-designteam-weirds-using-http-00.txt (Friday, 11 May)
• Fwd: RFC 6585 on Additional HTTP Status Codes (Monday, 30 April)
• Re: HTTP status code for "response too large" (Wednesday, 18 April)
• Re: HTTP status code for "response too large" (Wednesday, 18 April)
• Re: HTTP status code for "response too large" (Wednesday, 18 April)
• Re: Portal authorization (Tuesday, 10 April)
• Re: Portal authorization (Tuesday, 10 April)
• Re: Portal authorization (Tuesday, 10 April)

Karl Dubost

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Some thoughts on server push and client pull (Friday, 8 June)
• Re: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)
• Re: SPDY = HTTP/2.0 or not ? (Tuesday, 3 April)

Kornel Lesiński

• enc: URL scheme (Wednesday, 13 June)

lionel.morand@orange.com

• RE: Reminder: Call for Proposals - HTTP Authentication (Wednesday, 2 May)
• RE: Reminder: Call for Proposals - HTTP Authentication (Tuesday, 1 May)
• RE: Reminder: Call for Proposals - HTTP Authentication (Monday, 30 April)
• RE: Reminder: Call for Proposals - HTTP Authentication (Friday, 27 April)

Ludin, Stephen

• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 1 June)

Manger, James H

• RE: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• RE: WGLC #348: Realms and scope (Thursday, 7 June)
• RE: WGLC #348: Realms and scope (Monday, 4 June)

Mark Baker

• Re: #290: Motivate one-year limit for Expires (Saturday, 28 April)

Mark Nottingham

• Re: #271: use of "may" and "should" (Friday, 29 June)
• Re: WGLC #363: rare cases (Wednesday, 27 June)
• Re: WGLC #354 - ETags & conditional requests (Wednesday, 27 June)
• Re: WGLC #363: rare cases (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Advice to define where new status codes can be generated (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Advice to define where new status codes can be generated (Tuesday, 26 June)
• #350: WGLC Issue for p4: Optionality of Conditional Request Support (Monday, 25 June)
• Advice to define where new status codes can be generated (Monday, 25 June)
• Re: #307 (untangle Cache-Control ABNF) (Sunday, 24 June)
• WGLC #363: rare cases (Sunday, 24 June)
• Re: #271: SHOULD review in p7 (Sunday, 24 June)
• Re: WGLC #354 - ETags & conditional requests (Saturday, 23 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• #271: SHOULD review in p7 (Friday, 22 June)
• #271: SHOULD review in p5 (Friday, 22 June)
• #271: SHOULD review in p4 (Friday, 22 June)
• Re: WGLC #354 - ETags & conditional requests (Friday, 22 June)
• Re: #347: clarify that 201 can imply *multiple* resources were created (Thursday, 21 June)
• WGLC #354 - ETags & conditional requests (Thursday, 21 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Thursday, 21 June)
• #347: clarify that 201 can imply *multiple* resources were created (Thursday, 21 June)
• Call for Expressions of Interest in Proposals for HTTP/2.0 and New HTTP Authentication Schemes (Thursday, 21 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: #361: ABNF requirements for recipients [was: #307 untangle Cache-Control ABNF] (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: #361: ABNF requirements for recipients [was: #307 untangle Cache-Control ABNF] (Tuesday, 19 June)
• #367: ABNF requirements for recipients [was: #307 untangle Cache-Control ABNF] (Tuesday, 19 June)
• Re: #307 (untangle Cache-Control ABNF) (Tuesday, 19 June)
• Re: #307 (untangle Cache-Control ABNF) (Tuesday, 19 June)
• Re: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• Re: WGLC #357: Authentication Exchanges (Thursday, 14 June)
• Re: inv-maxage Cache-Control directive syntax, was: Fwd: I-D Action: draft-nottingham-linked-cache-inv-00.txt (Thursday, 14 June)
• Re: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• Re: #307 (untangle Cache-Control ABNF) (Thursday, 14 June)
• Re: enc: URL scheme (Thursday, 14 June)
• Vancouver in July (Thursday, 14 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: #307 (untangle Cache-Control ABNF) (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: #307 (untangle Cache-Control ABNF) (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Tuesday, 12 June)
• Re: Proposing Status Codes (Tuesday, 12 June)
• Proposing Status Codes (Monday, 11 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: #307 (untangle Cache-Control ABNF) (Monday, 11 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Sunday, 10 June)
• Re: Some thoughts on server push and client pull (Friday, 8 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 8 June)
• #247: "intended usage" in our registries (Friday, 8 June)
• Re: #346: Registry policies (Friday, 8 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 8 June)
• WGLC #357: Authentication Exchanges (Friday, 8 June)
• Re: WGLC #349: "strength" (Friday, 8 June)
• Re: WGLC #348: Realms and scope (Friday, 8 June)
• Re: Some thoughts on server push and client pull (Friday, 8 June)
• Reminder: Proposals for HTTP/2.0, Authentication Schemes Due (Friday, 8 June)
• Re: FYI: LCI -02 (Monday, 4 June)
• Re: FYI: LCI -02 (Monday, 4 June)
• Re: WGLC #349: "strength" (Monday, 4 June)
• Re: WGLC #348: Realms and scope (Monday, 4 June)
• Re: WGLC #349: "strength" (Monday, 4 June)
• Re: WGLC #349: "strength" (Monday, 4 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 1 June)
• FYI: LCI -02 (Friday, 1 June)
• Re: WGLC #349: "strength" (Friday, 1 June)
• Re: WGLC #349: "strength" (Friday, 1 June)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• WGLC #349: "strength" (Thursday, 31 May)
• WGLC #348: Realms and scope (Thursday, 31 May)
• WGLC #353: Multiple Values in Cache-Control headers (Thursday, 31 May)
• Re: Forward proxies and CDN/mirrors (Monday, 21 May)
• Re: Review of draft-ietf-httpbis-p7-auth-19.txt (Wednesday, 9 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Wednesday, 2 May)
• Fwd: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Tuesday, 1 May)
• Re: Reminder: Call for Proposals - HTTP Authentication (Tuesday, 1 May)
• Re: Reminder: Call for Proposals - HTTP Authentication (Tuesday, 1 May)
• Re: #290: Motivate one-year limit for Expires (Saturday, 28 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Last-Modified header in 304 and 206 responses (Wednesday, 25 April)
• #266: Header Microsyntax (Wednesday, 25 April)
• #340: Tolerating CR (Wednesday, 25 April)
• #322: Origin (Wednesday, 25 April)
• Re: WGLC issue: P4 - ETags & conditional requests (Wednesday, 25 April)
• Re: WGLC issue: P6 - Multiple values in Cache-Control headers (Wednesday, 25 April)
• Re: Comments/Issues on P1 (Tuesday, 24 April)
• IETF 83 - rough minutes (Tuesday, 24 April)
• Re: HTTP status code for "response too large" (Wednesday, 18 April)
• Re: Some proxy needs (Monday, 9 April)
• Re: FYI: CORS Last Call (Friday, 6 April)
• FYI: CORS Last Call (Friday, 6 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)

Mark Watson

• Re: Backwards compatibility (Monday, 2 April)

Markus.Isomaki@nokia.com

• RE: Reminder: Call for Proposals - HTTP Authentication (Thursday, 3 May)
• RE: 2.0 and Radio Impacts/battery efficiency (Friday, 13 April)

Martin J. Dürst

• Portal authorization (was: Re: multiplexing -- don't do it) (Tuesday, 10 April)

Martin Nilsson

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: Significantly reducing headers footprint (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: SPDY Review (Monday, 11 June)
• Re: SPDY Review (Monday, 11 June)
• Re: SPDY Review (Friday, 8 June)
• Re: SPDY Review (Friday, 8 June)
• Re: SPDY Review (Friday, 8 June)
• Re: SPDY Review (Friday, 8 June)
• Re: SPDY Review (Friday, 8 June)
• SPDY Review (Thursday, 7 June)

Martin Thomson

• Re: Status code for censorship? (Sunday, 10 June)
• Re: Some thoughts on server push and client pull (Friday, 8 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Re: SPDY Review (Thursday, 7 June)
• Re: WGLC #348: Realms and scope (Wednesday, 6 June)
• Re: WGLC #348: Realms and scope (Monday, 4 June)
• Re: WGLC #353: Multiple Values in Cache-Control headers (Friday, 1 June)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Tuesday, 3 April)

Mike Belshe

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• Re: Significantly reducing headers footprint (Monday, 11 June)
• Re: SPDY Review (Saturday, 9 June)
• Re: SPDY Review (Friday, 8 June)
• Re: SPDY Review (Friday, 8 June)
• Re: SPDY Review (Friday, 8 June)
• Re: multiplexing over more than one connection (Friday, 8 June)
• Re: Some thoughts on server push and client pull (Friday, 8 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• FalseStart - another protocol tweak that failed (Wednesday, 11 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Saturday, 7 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Saturday, 7 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: HTTP -> Messages -> Transport factoring (Friday, 6 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)

Murray S. Kucherawy

• RE: Proposal to make draft-kucherawy-httpbis-summary a WG document (Monday, 2 April)

Musatov, Martin - CW

• RE: #271: use of "may" and "should" (Monday, 25 June)
• RE: Status code for censorship? (Monday, 11 June)
• RE: Status code for censorship? (Monday, 11 June)
• RE: WGLC #349: "strength" (Monday, 4 June)
• RE: WGLC #349: "strength" (Thursday, 31 May)
• RE: part 2, 5.1 "the response payload is a representation of the target resource" (Wednesday, 23 May)
• RE: add GETAJAX verb/method in http protocol (Tuesday, 22 May)

Nicolas Mailhot

• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Wednesday, 2 May)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Portal authorization (Tuesday, 10 April)
• Re: Re[2]: Some proxy needs (Tuesday, 10 April)
• Re: Portal authorization (was: Re: multiplexing -- don't do it) (Tuesday, 10 April)
• Re: Portal authorization (was: Re: multiplexing -- don't do it) (Tuesday, 10 April)
• Re: Re[2]: Some proxy needs (Tuesday, 10 April)
• Re: multiplexing -- don't do it (Tuesday, 10 April)
• Re: Re[2]: Some proxy needs (Sunday, 8 April)
• Re: Re[2]: Some proxy needs (Sunday, 8 April)
• Re: Some proxy needs (Sunday, 8 April)
• Re: Re[2]: Some proxy needs (Sunday, 8 April)
• Some proxy needs (Sunday, 8 April)
• Re: multiplexing -- don't do it (Sunday, 8 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: Adjusting our spec names (Friday, 6 April)

order-update@amazon.com

• Amazon.com - Your Cancellation (12-612-4143) (Wednesday, 2 May)

Patrick McManus

• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Monday, 25 June)
• Re: Significantly reducing headers footprint (Monday, 11 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Re: multiplexing -- don't do it (Saturday, 7 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)

Paul Hoffman

• Re: Proposal to make draft-kucherawy-httpbis-summary a WG document (Tuesday, 3 April)
• NEW ISSUE: httpbis-p1 updates RFC 2818 as well (editorial) (Monday, 2 April)
• Re: Proposal to make draft-kucherawy-httpbis-summary a WG document (Monday, 2 April)
• Proposal to make draft-kucherawy-httpbis-summary a WG document (Monday, 2 April)

Per Buer

• Re: Re[2]: Some proxy needs (Tuesday, 10 April)
• Re: Re[2]: Some proxy needs (Tuesday, 10 April)
• Re: Re[2]: Some proxy needs (Monday, 9 April)

Peter L

• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: Re[2]: multiplexing -- don't do it (Sunday, 1 April)

Peter Lepeska

• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Monday, 7 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Friday, 4 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Friday, 4 May)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Monday, 30 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Monday, 30 April)
• Re: multiplexing -- don't do it (Saturday, 7 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)
• Re: multiplexing -- don't do it (Sunday, 1 April)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)
• Ascii-based SPDY "compression" idea (Sunday, 1 April)

Peter Saint-Andre

• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Re: WGLC issue: following HTTP redirects (Monday, 4 June)
• Re: WGLC issue: following HTTP redirects (Monday, 4 June)
• WGLC issue: following HTTP redirects (Friday, 1 June)

Poul-Henning Kamp

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Sunday, 24 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: New Version Notification for draft-montenegro-httpbis-speed-mobility-02.txt (Saturday, 23 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• Re: New Version Notification for draft-montenegro-httpbis-speed-mobility-02.txt (Friday, 22 June)
• Re: SPDY Review (Monday, 11 June)
• Re: FYI: LCI -02 (Monday, 4 June)
• Re: add GETAJAX verb/method in http protocol (Tuesday, 22 May)
• Re: add GETAJAX verb/method in http protocol (Tuesday, 22 May)
• Re: Re[2]: Some proxy needs (Sunday, 8 April)
• Re: Re[2]: Some proxy needs (Sunday, 8 April)
• Re: Some proxy needs (Sunday, 8 April)
• Re: Re[2]: multiplexing -- don't do it (Saturday, 7 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: FYI: CORS Last Call (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: Make HTTP 2.0 message/transport format agnostic (Sunday, 1 April)

Rajeev Bector

• Re: Some thoughts on server push and client pull (Friday, 8 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)

Ray

• Re: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)

Ray Polk

• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: WGLC Issue for p4: Optionality of Conditional Request Support (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)

Rob Trace

• New Version Notification for draft-montenegro-httpbis-speed-mobility-02.txt (Tuesday, 19 June)

Robert Collins

• Re: Re[3]: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)

Robert Mattson

• RE: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: multiplexing over more than one connection (Friday, 8 June)
• Improving page retrieval time (Tuesday, 15 May)

Roberto Peon

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• Re: Proposing Status Codes (Tuesday, 12 June)
• Re: Significantly reducing headers footprint (Sunday, 10 June)
• Re: Explicit Proxy (draft-rpeon-httpbis-exproxy) (Sunday, 10 June)
• Re: multiplexing different hosts on a single SSL connections (Friday, 8 June)
• Re: multiplexing different hosts on a single SSL connections (Friday, 8 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Re: SPDY Review (Thursday, 7 June)
• Re: 2.0 and Radio Impacts/battery efficiency (Sunday, 15 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Sunday, 15 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Saturday, 14 April)
• RE: 2.0 and Radio Impacts/battery efficiency (Friday, 13 April)
• RE: 2.0 and Radio Impacts/battery efficiency (Friday, 13 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Friday, 13 April)
• Re: Re[2]: Some proxy needs (Tuesday, 10 April)
• Re: multiplexing -- don't do it (Saturday, 7 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: Backwards compatibility (Tuesday, 3 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: multiplexing -- don't do it (Sunday, 1 April)

Ross Nicoll

• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)

Roy T. Fielding

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: WGLC issue: P4 - ETags & conditional requests (Monday, 23 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)

Safruti, Ido

• Re: multiplexing different hosts on a single SSL connections (Friday, 8 June)
• multiplexing different hosts on a single SSL connections (Friday, 8 June)
• multiplexing over more than one connection (Friday, 8 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)

Salvatore Loreto

• Re: 2.0 and Radio Impacts/battery efficiency (Friday, 13 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Friday, 13 April)
• 2.0 and Radio Impacts/battery efficiency (Thursday, 12 April)
• Re: multiplexing -- don't do it (Tuesday, 10 April)

Stefan Lederer

• RE: SPDY = HTTP/2.0 or not ? (Wednesday, 4 April)

Stephane Bortzmeyer

• Re: Status code for censorship? (Sunday, 10 June)

Stephen Farrell

• Fwd: New Version Notification for draft-farrell-httpbis-hoba-00.txt (Wednesday, 13 June)
• Re: Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: WGLC #349: "strength" (Monday, 4 June)
• Re: WGLC #349: "strength" (Thursday, 31 May)
• Re: WGLC #349: "strength" (Thursday, 31 May)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)

Tim Bray

• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Friday, 15 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Tuesday, 12 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Tuesday, 12 June)
• Fwd: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Tuesday, 12 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Monday, 11 June)
• Re: Status code for censorship? (Sunday, 10 June)
• Status code for censorship? (Sunday, 10 June)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)
• Re: Make HTTP 2.0 message/transport format agnostic (Sunday, 1 April)

tom

• Re: multiplexing -- don't do it (Saturday, 7 April)
• Re: multiplexing -- don't do it (Saturday, 7 April)
• Re: multiplexing -- don't do it (Saturday, 7 April)

William A. Rowe Jr.

• Re: httpbis-method-registrations (Thursday, 7 June)
• httpbis-method-registrations (Thursday, 7 June)

Willy Tarreau

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Saturday, 23 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Thursday, 14 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: New Version Notification for draft-tbray-http-legally-restricted-status-00.txt (Wednesday, 13 June)
• Re: Significantly reducing headers footprint (Monday, 11 June)
• Re: Significantly reducing headers footprint (Monday, 11 June)
• Re: Significantly reducing headers footprint (Monday, 11 June)
• Re: Significantly reducing headers footprint (Monday, 11 June)
• Significantly reducing headers footprint (Sunday, 10 June)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Tuesday, 15 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Tuesday, 15 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Monday, 14 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Monday, 14 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt - section 5.1 (Sunday, 6 May)
• Re: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Wednesday, 2 May)
• Re: Fwd: WGLC: draft-ietf-appsawg-http-forwarded-02.txt (Wednesday, 2 May)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Friday, 27 April)
• Re: Comments/Issues on P1 (Tuesday, 24 April)
• Re: Comments/Issues on P1 (Tuesday, 24 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Saturday, 14 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: HTTP -> Messages -> Transport factoring (Thursday, 5 April)
• Re: options or protocols? (Thursday, 5 April)
• Re: options or protocols? (Thursday, 5 April)
• Re: options or protocols? (Thursday, 5 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: multiplexing -- don't do it (Wednesday, 4 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Tuesday, 3 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Re[2]: multiplexing -- don't do it (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: Adjusting our spec names (Sunday, 1 April)
• Re: multiplexing -- don't do it (Sunday, 1 April)

wrong string

• Re: enc: URL scheme (Thursday, 14 June)

Yi, EungJun

• Re: Status code for censorship? (Monday, 11 June)

Yoav Nir

• Re: Status code for censorship? (Sunday, 10 June)
• Explicit Proxy (draft-rpeon-httpbis-exproxy) (Sunday, 10 June)
• RE: Status code for censorship? (Sunday, 10 June)

Yuchung Cheng

• Re: multiplexing over more than one connection (Friday, 8 June)

Yutaka OIWA

• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Wednesday, 20 June)
• Re: WGLC #357: Authentication Exchanges (Thursday, 14 June)
• Re: Comments on draft-oiwa-httpbis-auth-extension-00 (Thursday, 14 June)
• Re: [httpauth] Mutual authentication proposal (Wednesday, 13 June)
• Re: [httpauth] Mutual authentication proposal (Tuesday, 5 June)
• [httpauth] Mutual authentication proposal (Monday, 4 June)
• Re: WGLC #348: Realms and scope (Thursday, 31 May)
• http-auth: Mutual - drafts updated (Monday, 21 May)

Zhong Yu

• Re: WGLC #354 - ETags & conditional requests (Thursday, 21 June)
• Re: Last-Modified header in 304 and 206 responses (Friday, 13 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Thursday, 12 April)
• Last-Modified header in 304 and 206 responses (Friday, 6 April)

イアンフェッティ

• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)

陈智昌

• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Tuesday, 26 June)
• Re: Performance implications of Bundling and Minification on HTTP/1.1 (Friday, 22 June)
• Re: SPDY Review (Thursday, 7 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Re: Some thoughts on server push and client pull (Thursday, 7 June)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Monday, 30 April)
• Re: Reminder: Call for Proposals - HTTP/2.0 and HTTP Authentication (Monday, 30 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Sunday, 15 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Saturday, 14 April)
• Re: 2.0 and Radio Impacts/battery efficiency (Saturday, 14 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Friday, 6 April)
• Re: multiplexing -- don't do it (Friday, 6 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: options or protocols? (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Thursday, 5 April)
• Re: multiplexing -- don't do it (Tuesday, 3 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: breaking TLS (Was: Re: multiplexing -- don't do it) (Monday, 2 April)
• Re: Backwards compatibility (Monday, 2 April)
• Re: multiplexing -- don't do it (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Ascii-based SPDY "compression" idea (Monday, 2 April)
• Re: Re[4]: multiplexing -- don't do it (Sunday, 1 April)
• Re: Protocols, extensions, compatibility (Sunday, 1 April)
• Re: Ascii-based SPDY "compression" idea (Sunday, 1 April)

Last message date: Friday, 29 June 2012 15:53:31 UTC