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

Tuesday, 30 June 2015

• Re: Range Responses of Indeterminate Length: Draft Plex
• Re: Confirmation of list posting -- confirmation ID: VZIWxgENjJWZ The ietf.org mailing-list server has received a list posting from milliem27.mm@gmail.com to xfilter-draft-ietf-httpbis-legally-restricted-status@ietfa.amsl.com with the subject 'xfilter-draft-ietf-httpbis-legally-restricted-status@ietfa.amsl.com' As the sender address isn't subscribed to the list, and has not been confirmed earlier, we have to request a confirmation of the address. To confirm the address, send a message to xfilter-draft-ietf-httpbis-legally-restricted-status@ietfa.amsl.com, with the same subject line as this message. (Simply sending a 'reply' to this message should work from most email interfaces, since that usually leaves the subject line in the right form. The reply's additional "Re:" is ok.) If you do not wish your posting to the list to go through, simply disregard this message. Questions to postmaster@ietf.org. Mel
• RE: Confirmation of list posting -- confirmation ID: VZIWxgENjJWZ The ietf.org mailing-list server has received a list posting from milliem27.mm@gmail.com to xfilter-draft-ietf-httpbis-legally-restricted-status@ietfa.amsl.com with the subject 'xfilter-draft-ietf-httpbis-legally-restricted-status@ietfa.amsl.com' As the sender address isn't subscribed to the list, and has not been confirmed earlier, we have to request a confirmation of the address. To confirm the address, send a message to xfilter-draft-ietf-httpbis-legally-restricted-status@ietfa.amsl.com, with the same subject line as this message. (Simply sending a 'reply' to this message should work from most email interfaces, since that usually leaves the subject line in the right form. The reply's additional "Re:" is ok.) If you do not wish your posting to the list to go through, simply disregard this message. Questions to postmaster@ietf.org. Mel

Monday, 29 June 2015

• Stephen Farrell's No Objection on draft-ietf-httpbis-tunnel-protocol-05: (with COMMENT) Stephen Farrell

Sunday, 28 June 2015

• I-D Action: draft-ietf-httpbis-legally-restricted-status-01.txt internet-drafts@ietf.org

Friday, 26 June 2015

• Re: Kerberos Authentication question(s) Michael B Allen
• Re: Kerberos Authentication question(s) Isaac Boukris
• Re: Kerberos Authentication question(s) Amos Jeffries

Thursday, 25 June 2015

• Re: Kerberos Authentication question(s) Michael B Allen

Wednesday, 24 June 2015

• Re: Client Explicitly Requesting an Empty Body Brad Fults
• Re: Client Explicitly Requesting an Empty Body Martin Thomson
• Client Explicitly Requesting an Empty Body Brad Fults
• Re: Browser display of 403 responses bodies on CONNECT Amos Jeffries
• Re: Browser display of 403 responses bodies on CONNECT Roland Zink
• Re: Browser display of 403 responses bodies on CONNECT Roland Zink
• Re: Browser display of 403 responses bodies on CONNECT Nicolas Mailhot
• Re: Browser display of 403 responses bodies on CONNECT Adrien de Croy
• Re: Browser display of 403 responses bodies on CONNECT Nicolas Mailhot
• Re: Prague agenda Martin Thomson

Tuesday, 23 June 2015

• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: Browser display of 403 responses bodies on CONNECT Francesco Chemolli
• Re: First cut at an agenda for Prague Mark Nottingham
• Re: First cut at an agenda for Prague Martin J. Dürst
• Re: Browser display of 403 responses bodies on CONNECT Willy Tarreau
• Re: Browser display of 403 responses bodies on CONNECT Adrien de Croy
• Re: Browser display of 403 responses bodies on CONNECT Mark Nottingham
• First cut at an agenda for Prague Mark Nottingham

Monday, 22 June 2015

• Re: Prague agenda Mark Nottingham
• Re: I-D Action: draft-reschke-http-oob-encoding-00.txt Salvatore Loreto
• RE: Fwd: I-D Action: draft-reschke-http-oob-encoding-00.txt Mike Bishop
• Re: Prague agenda Martin Thomson
• Re: I-D Action: draft-reschke-http-oob-encoding-00.txt Julian Reschke
• Re: Prague agenda Julian Reschke
• Prague agenda Mark Nottingham

Sunday, 21 June 2015

• Re: I-D Action: draft-reschke-http-oob-encoding-00.txt John Mattsson
• Re: Fwd: I-D Action: draft-reschke-http-oob-encoding-00.txt Julian Reschke
• Re: SRV in HTTP/2 Mark Nottingham
• Re: New Version Notification for draft-thomson-http-encryption-00.txt John Mattsson
• SRV in HTTP/2 Max Bruce

Saturday, 20 June 2015

• Re: NEW PREFERENCE - vtimezone Amos Jeffries
• Re: NEW PREFERENCE - vtimezone Cyrus Daboo
• Re: NEW PREFERENCE - vtimezone Amos Jeffries

Friday, 19 June 2015

• Re: NEW PREFERENCE - vtimezone Cyrus Daboo
• Re: NEW PREFERENCE - vtimezone Martin Thomson
• NEW PREFERENCE - vtimezone Daniel Migault
• draft-ietf-httpbis-http2-latest, "5.3.1 Stream Dependencies" raylillywhite@gmail.com

Thursday, 18 June 2015

• Re: http/1 opportunistic encryption Martin Thomson
• Re: Browser display of 403 responses bodies on CONNECT Willy Tarreau
• Re: http/1 opportunistic encryption Stefan Eissing
• Re: http/1 opportunistic encryption Stefan Eissing
• Re: Browser display of 403 responses bodies on CONNECT Adrien de Croy
• Re: Browser display of 403 responses bodies on CONNECT Willy Tarreau
• Re: Browser display of 403 responses bodies on CONNECT Amos Jeffries
• Re: Browser display of 403 responses bodies on CONNECT Amos Jeffries
• Re: Browser display of 403 responses bodies on CONNECT Adrien de Croy
• Re: Browser display of 403 responses bodies on CONNECT Martin Thomson
• Re: Browser display of 403 responses bodies on CONNECT Adrien de Croy
• Re: Browser display of 403 responses bodies on CONNECT Adrien de Croy

Wednesday, 17 June 2015

• Re: Browser display of 403 responses bodies on CONNECT Martin Thomson
• HTTP/2 Hackathon in Prague Mark Nottingham
• Browser display of 403 responses bodies on CONNECT Adrien de Croy
• Re: http/1 opportunistic encryption Martin Thomson
• Re: #75: 421 Status with Alt-Svc Header Patrick McManus
• Re: http/1 opportunistic encryption Stefan Eissing
• Re: http/1 opportunistic encryption Ilari Liusvaara
• Re: http/1 opportunistic encryption Stefan Eissing
• Re: http/1 opportunistic encryption Mark Nottingham

Tuesday, 16 June 2015

• Re: #73: Alt-Svc Elevation of Privilege Martin Thomson
• Re: #73: Alt-Svc Elevation of Privilege Erik Nygren
• RE: #73: Alt-Svc Elevation of Privilege Mike Bishop
• Re: http/1 opportunistic encryption Patrick McManus
• http/1 opportunistic encryption Stefan Eissing
• Re: #75: 421 Status with Alt-Svc Header Martin Thomson
• Re: I-D Action: draft-ietf-httpbis-http2-encryption-02.txt Martin Thomson
• #75: 421 Status with Alt-Svc Header Mark Nottingham
• Re: #74: Alternates of Alternates Mark Nottingham
• Re: #73: Alt-Svc Elevation of Privilege Mark Nottingham
• I-D Action: draft-ietf-httpbis-http2-encryption-02.txt internet-drafts@ietf.org

Friday, 12 June 2015

• Re: Alt-Svc #62: proxies Martin Thomson
• Re: Alt-Svc #62: proxies Roland Zink
• Re: Alt-Svc #62: proxies Martin Thomson
• Re: Alt-Svc #62: proxies Roland Zink
• Re: Alt-Svc #62: proxies Martin Thomson

Thursday, 11 June 2015

• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Spencer Dawkins at IETF

Friday, 12 June 2015

• Re: Alt-Svc #62: proxies Roland Zink
• Re: Alt-Svc #62: proxies Ryan Hamilton
• Re: Alt-Svc #62: proxies Mark Nottingham
• Re: alpn identifiers (not again!) Matthew Kerwin
• Re: alpn identifiers (not again!) Martin Thomson
• Re: Alt-Svc #62: proxies Amos Jeffries

Thursday, 11 June 2015

• Re: alpn identifiers (not again!) Amos Jeffries
• Re: Alt-Svc #62: proxies Martin Thomson
• [Errata Rejected] RFC7233 (4391) RFC Errata System
• Re: [Technical Errata Reported] RFC7233 (4391) Roy T. Fielding
• [Technical Errata Reported] RFC7233 (4391) RFC Errata System
• I-D Action: draft-ietf-httpbis-tunnel-protocol-05.txt internet-drafts@ietf.org
• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Martin Thomson
• Re: Spencer Dawkins' No Objection on draft-ietf-httpbis-tunnel-protocol-04: (with COMMENT) Martin Thomson
• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Barry Leiba
• Re: Alt-Svc #62: proxies Ryan Hamilton
• Re: #72: Conflicts between Alt-Svc and ALPN Ryan Hamilton
• Re: Spencer Dawkins' No Objection on draft-ietf-httpbis-tunnel-protocol-04: (with COMMENT) Spencer Dawkins at IETF
• Re: alpn identifiers (not again!) Martin Thomson
• Re: alpn identifiers (not again!) Matthew Kerwin
• Re: alpn identifiers (not again!) Adrien de Croy
• [OT] thanks Matthew Kerwin

Wednesday, 10 June 2015

• Re: alpn identifiers (not again!) Martin Thomson
• Re: alpn identifiers (not again!) Adrien de Croy
• Re: alpn identifiers (not again!) Martin Thomson
• Re: alpn identifiers (not again!) Adrien de Croy
• Re: Spencer Dawkins' No Objection on draft-ietf-httpbis-tunnel-protocol-04: (with COMMENT) Martin Thomson
• Re: alpn identifiers (not again!) Martin Thomson
• Re: Registering New Prefer Header James M Snell
• Re: Registering New Prefer Header Barry Leiba
• Registering New Prefer Header Daniel Migault
• RE: alpn identifiers (not again!) Lucas Pardue
• Re: alpn identifiers (not again!) Stefan Eissing
• Re: [Moderator Action] Kathleen Moriarty's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Kathleen Moriarty

Tuesday, 9 June 2015

• Kathleen Moriarty's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Kathleen Moriarty

Wednesday, 10 June 2015

• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Mark Nottingham
• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Adrien de Croy
• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Amos Jeffries

Tuesday, 9 June 2015

• RE: HPACK, Dynamic Table Size Update Mike Bishop
• Re: Alt-Svc #62: proxies Mark Nottingham
• Re: #72: Conflicts between Alt-Svc and ALPN Mark Nottingham
• RE: Client certificates in HTTP/2 Mike Bishop
• RE: Client certificates in HTTP/2 Mike Bishop
• Re: Client certificates in HTTP/2 Adrien de Croy
• Re: Client certificates in HTTP/2 Martin Thomson
• Re: Client certificates in HTTP/2 Adrien de Croy
• Re: Client certificates in HTTP/2 Martin Thomson
• Re: Kathleen Moriarty's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Martin Thomson
• Re: Client certificates in HTTP/2 Adrien de Croy
• Re: Client certificates in HTTP/2 Martin Thomson
• Re: Client certificates in HTTP/2 Adrien de Croy
• Re: HPACK, Dynamic Table Size Update Martin Thomson
• Re: alpn identifiers (not again!) Martin Thomson
• Re: Client certificates in HTTP/2 Adrien de Croy
• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Martin Thomson
• Re: HPACK, Dynamic Table Size Update Pavel Rappo
• Re: Client certificates in HTTP/2 Yoav Nir
• Re: alpn identifiers (not again!) Roy T. Fielding
• Re: Client certificates in HTTP/2 Ilari Liusvaara
• RE: Client certificates in HTTP/2 Mike Bishop
• RE: alpn identifiers (not again!) Mike Bishop
• Re: alpn identifiers (not again!) Stefan Eissing
• Re: HPACK, Dynamic Table Size Update Martin Thomson
• RE: HPACK, Dynamic Table Size Update Mike Bishop
• Re: alpn identifiers (not again!) Martin Thomson
• HPACK, Dynamic Table Size Update Pavel Rappo
• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Stephen Farrell
• Re: alpn identifiers (not again!) Stefan Eissing
• Client certificates in HTTP/2 Yoav Nir
• Re: #80: 451 / distinguishing intermediaries from origins Mark Nottingham
• Re: #80: 451 / distinguishing intermediaries from origins Tim Bray
• Re: #73: Alt-Svc Elevation of Privilege Martin Thomson
• Re: Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Mark Nottingham
• Re: #73: Alt-Svc Elevation of Privilege Mark Nottingham

Monday, 8 June 2015

• Re: Alt-Svc #71: Hints for Flushing Martin Thomson
• Re: Alt-Svc #71: Hints for Flushing Erik Nygren
• Re: #80: 451 / distinguishing intermediaries from origins Ted Hardie
• Re: #73: Alt-Svc Elevation of Privilege Martin Thomson
• Re: alpn identifiers (not again!) Martin Thomson
• Re: #73: Alt-Svc Elevation of Privilege Patrick McManus
• Re: #73: Alt-Svc Elevation of Privilege Ryan Hamilton
• Re: #73: Alt-Svc Elevation of Privilege Patrick McManus
• alpn identifiers (not again!) Stefan Eissing
• Stephen Farrell's Discuss on draft-ietf-httpbis-tunnel-protocol-04: (with DISCUSS and COMMENT) Stephen Farrell
• Re: Alt-Svc #62: proxies Patrick McManus
• Re: #72: Conflicts between Alt-Svc and ALPN Patrick McManus
• Re: Working Group Last Call for draft-ietf-httpbis-cice (Client-Initiated Content-Encoding) Amos Jeffries
• #80: 451 / distinguishing intermediaries from origins Mark Nottingham
• #73: Alt-Svc Elevation of Privilege Mark Nottingham
• #74: Alternates of Alternates Mark Nottingham
• #72: Conflicts between Alt-Svc and ALPN Mark Nottingham
• Re: Alt-Svc #71: Hints for Flushing Mark Nottingham
• Re: Alt-Svc #62: proxies Mark Nottingham
• Working Group Last Call for draft-ietf-httpbis-cice (Client-Initiated Content-Encoding) Mark Nottingham

Thursday, 4 June 2015

• Fwd: I-D Action: draft-reschke-http-oob-encoding-00.txt Julian Reschke
• Re: Alt-Svc #71: Hints for Flushing Patrick McManus
• RE: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Christer Holmberg
• Re: Alt-Svc #71: Hints for Flushing Erik Nygren
• Re: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Barry Leiba
• Re: Alt-Svc #71: Hints for Flushing Ryan Hamilton

Wednesday, 3 June 2015

• Re: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Martin Thomson
• Re: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Barry Leiba

Tuesday, 2 June 2015

• Re: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Julian Reschke
• Re: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Martin Thomson
• RE: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Christer Holmberg
• Re: Alt-Svc #71: Hints for Flushing Mark Nottingham

Monday, 1 June 2015

• Re: Alt-Svc #71: Hints for Flushing Martin Thomson
• Re: Partial header indexing in HPACK? Brendan Long
• [Errata Rejected] RFC7231 (4351) RFC Errata System
• Re: Proposed HTTP SEARCH method update Eric Prud'hommeaux
• Re: Alt-Svc #62: proxies Amos Jeffries
• Re: same connection, different hosts Amos Jeffries
• Alt-Svc #71: Hints for Flushing Mark Nottingham
• Alt-Svc #62: proxies Mark Nottingham
• Re: #69: Alt-Svc extension parameters Mark Nottingham

Sunday, 31 May 2015

• Re: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Julian Reschke
• RE: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Christer Holmberg

Saturday, 30 May 2015

• Re: same connection, different hosts Glen Knowles
• Re: draft-ietf-httpbis-tunnel-protocol-04, "4. Security Considerations" Martin Thomson
• Re: draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Martin Thomson
• draft-ietf-httpbis-tunnel-protocol-04, "4. Security Considerations" Julian Reschke
• draft-ietf-httpbis-tunnel-protocol-04, "2.2 Syntax" Julian Reschke
• Re: CICE edits / call for other issues Julian Reschke
• I-D Action: draft-ietf-httpbis-cice-01.txt internet-drafts@ietf.org
• Re: same connection, different hosts Amos Jeffries

Friday, 29 May 2015

• Re: Partial header indexing in HPACK? Martin Thomson
• Re: same connection, different hosts Erik Nygren
• Partial header indexing in HPACK? Brendan Long
• Re: 204 no content response with Content-Length header. Amos Jeffries
• Re: 204 no content response with Content-Length header. Willy Tarreau
• Re: 204 no content response with Content-Length header. Greg Wilkins
• Re: 204 no content response with Content-Length header. Willy Tarreau
• Re: 204 no content response with Content-Length header. Greg Wilkins

Thursday, 28 May 2015

• Fwd: New Version Notification for draft-hunt-scim-search-00.txt Phil Hunt
• Re: 204 no content response with Content-Length header. Willy Tarreau
• Re: 204 no content response with Content-Length header. Adrien de Croy
• Re: 204 no content response with Content-Length header. Adrien de Croy
• Re: 204 no content response with Content-Length header. Willy Tarreau
• 204 no content response with Content-Length header. Adrien de Croy
• Re: same connection, different hosts Stefan Eissing
• Re: Proposed HTTP SEARCH method update Wenbo Zhu
• Re: how do we achieve 305 Use proxy in http Mark Nottingham

Wednesday, 27 May 2015

• Alt-Svc Feedback Mike Bishop
• RE: same connection, different hosts Mike Bishop
• Re: same connection, different hosts Martin Thomson
• Re: #69: Alt-Svc extension parameters Martin Thomson
• same connection, different hosts Stefan Eissing
• how do we achieve 305 Use proxy in http Aravindan G
• Re: #69: Alt-Svc extension parameters Amos Jeffries
• CICE edits / call for other issues Mark Nottingham
• #69: Alt-Svc extension parameters Mark Nottingham
• Re: alt-svc issue 58: Number of alternate services used Mark Nottingham
• Re: Proposed HTTP SEARCH method update Phil Hunt

Tuesday, 26 May 2015

• Re: Proposed HTTP SEARCH method update Wenbo Zhu

Saturday, 23 May 2015

• Re: Proposed HTTP SEARCH method update Phil Hunt
• RE: Proposed HTTP SEARCH method update Appanasamy, Palanivelan

Friday, 22 May 2015

• Re: Proposed HTTP SEARCH method update Phil Hunt
• Re: Proposed HTTP SEARCH method update Wenbo Zhu
• Re: draft-thomson-http-encryption-00 - Logjam Martin Thomson
• Re: draft-thomson-http-encryption-00 - Logjam Ilari Liusvaara
• Re: draft-thomson-http-encryption-00 - Logjam Ilari Liusvaara
• Re: draft-thomson-http-encryption-00 - Logjam Stephen Farrell
• draft-thomson-http-encryption-00 - Logjam Amos Jeffries
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update Wenbo Zhu

Wednesday, 20 May 2015

• Last Call: <draft-ietf-httpbis-tunnel-protocol-04.txt> (The ALPN HTTP Header Field) to Proposed Standard The IESG
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• I-D Action: draft-ietf-httpbis-tunnel-protocol-04.txt internet-drafts@ietf.org
• Re: Proposed HTTP SEARCH method update Phil Hunt
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Barry Leiba
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Martin Thomson
• Re: Proposed HTTP SEARCH method update Roy T. Fielding
• Re: Proposed HTTP SEARCH method update Zhong Yu
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update Wenbo Zhu
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update Wenbo Zhu
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update Amos Jeffries
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Mark Nottingham
• Re: Proposed HTTP SEARCH method update Phil Hunt
• Re: Proposed HTTP SEARCH method update Zhong Yu

Tuesday, 19 May 2015

• Re: Proposed HTTP SEARCH method update Phil Hunt
• Re: Proposed HTTP SEARCH method update Wenbo Zhu

Sunday, 17 May 2015

• Re: Proposed HTTP SEARCH method update Phil Hunt
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net

Friday, 15 May 2015

• I-D Action: draft-ietf-httpbis-alt-svc-07.txt internet-drafts@ietf.org

Thursday, 14 May 2015

• RFC 7541 on HPACK: Header Compression for HTTP/2 rfc-editor@rfc-editor.org
• RFC 7540 on Hypertext Transfer Protocol Version 2 (HTTP/2) rfc-editor@rfc-editor.org

Wednesday, 13 May 2015

• Re: Signing HTTP (Was: New Version Notification for draft-thomson-http-encryption-00.txt) Martin Thomson
• Re: Signing HTTP (Was: New Version Notification for draft-thomson-http-encryption-00.txt) Nicolas Mailhot
• Re: [Technical Errata Reported] RFC7231 (4351) Mark Nottingham
• Re: [Technical Errata Reported] RFC7231 (4351) Willy Tarreau
• Re: [Technical Errata Reported] RFC7231 (4351) Amos Jeffries
• Re: Signing HTTP (Was: New Version Notification for draft-thomson-http-encryption-00.txt) Poul-Henning Kamp
• Re: Signing HTTP (Was: New Version Notification for draft-thomson-http-encryption-00.txt) Willy Tarreau
• Re: Signing HTTP (Was: New Version Notification for draft-thomson-http-encryption-00.txt) James M Snell

Tuesday, 12 May 2015

• Signing HTTP (Was: New Version Notification for draft-thomson-http-encryption-00.txt) Martin Thomson
• Re: [Errata Held for Document Update] RFC7233 (4358) Roy T. Fielding
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Barry Leiba
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Martin Thomson
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Barry Leiba
• Re: [Technical Errata Reported] RFC7231 (4351) Barry Leiba
• [Errata Held for Document Update] RFC7233 (4358) RFC Errata System
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Amos Jeffries
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Amos Jeffries
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Amos Jeffries
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Cyrus Daboo
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Stephen Farrell
• Re: Time Precision Poul-Henning Kamp
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Amos Jeffries
• Re: Fwd: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: Fwd: New Version Notification for draft-thomson-http-encryption-00.txt Amos Jeffries
• Re: New Version Notification for draft-thomson-http-encryption-00.txt Mark Nottingham
• Fwd: IETF 93 - Hackathon Information [includes HTTP/2 focus] Mark Nottingham
• Re: Fwd: New Version Notification for draft-thomson-http-encryption-00.txt Willy Tarreau
• Re: Time Precision Greg Wilkins
• Re: Fwd: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson

Monday, 11 May 2015

• Re: Proposed HTTP SEARCH method update Zhong Yu
• Re: Fwd: New Version Notification for draft-thomson-http-encryption-00.txt Amos Jeffries
• Re: Proposed HTTP SEARCH method update James M Snell
• Re: Proposed HTTP SEARCH method update Phil Hunt
• Fwd: New Version Notification for draft-thomson-http-encryption-00.txt Martin Thomson
• Re: Time Precision Sawood Alam
• Re: Time Precision Poul-Henning Kamp
• Re: Time Precision Sawood Alam
• Re: Time Precision Poul-Henning Kamp
• Time Precision Sawood Alam

Sunday, 10 May 2015

• Re: Clarification on stale-while-revalidate / stale-if-error Will Sargent

Friday, 8 May 2015

• Re: [Technical Errata Reported] RFC7233 (4358) Tim

Thursday, 7 May 2015

• Re: [Technical Errata Reported] RFC7233 (4358) Tim
• Re: [Technical Errata Reported] RFC7233 (4358) Tim

Sunday, 10 May 2015

• Re: Proposed HTTP SEARCH method update Henry Story
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net

Saturday, 9 May 2015

• Re: alternative service probability parameter Julian Reschke
• Re: Clarification on stale-while-revalidate / stale-if-error Mark Nottingham

Friday, 8 May 2015

• Re: alternative service probability parameter Erik Nygren
• Re: alternative service probability parameter Ryan Hamilton
• Re: alternative service probability parameter Amos Jeffries
• alternative service probability parameter Bence Béky
• Re: [Technical Errata Reported] RFC7233 (4358) Roy T. Fielding

Thursday, 7 May 2015

• Re: Clarification on stale-while-revalidate / stale-if-error Will Sargent
• Re: [Technical Errata Reported] RFC7233 (4358) Paul Hoffman
• Re: [Technical Errata Reported] RFC7233 (4358) Julian Reschke
• [Technical Errata Reported] RFC7233 (4358) RFC Errata System
• Re: Clarification on stale-while-revalidate / stale-if-error Amos Jeffries

Wednesday, 6 May 2015

• Clarification on stale-while-revalidate / stale-if-error Will Sargent

Monday, 4 May 2015

• RE: alt-svc issue 43: ALPN identifiers in Alt-Svc Mike Bishop
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Barry Leiba
• Re: Proposed HTTP SEARCH method update Philippe Mougin
• Re: alt-svc issue 43: ALPN identifiers in Alt-Svc Mark Nottingham
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Mark Nottingham

Saturday, 2 May 2015

• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Adrien de Croy

Friday, 1 May 2015

• Re: Proposed HTTP SEARCH method update ashok malhotra
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Martin Thomson
• RE: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Mike Bishop
• Re: alt-svc issue 43: ALPN identifiers in Alt-Svc Erik Nygren
• Re: AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Martin Thomson
• Re: Proposed HTTP SEARCH method update Phil Hunt
• AD Evaluation of draft-ietf-httpbis-tunnel-protocol-03 Barry Leiba

Thursday, 30 April 2015

• RE: alt-svc issue 43: ALPN identifiers in Alt-Svc Mike Bishop
• Re: alt-svc issue 43: ALPN identifiers in Alt-Svc Ryan Hamilton
• Re: alt-svc issue 43: ALPN identifiers in Alt-Svc Adrien de Croy
• RE: alt-svc issue 43: ALPN identifiers in Alt-Svc Mike Bishop
• Re: alt-svc issue 43: ALPN identifiers in Alt-Svc Julian Reschke
• Re: alt-svc issue 43: ALPN identifiers in Alt-Svc Hervé Ruellan
• alt-svc issue 43: ALPN identifiers in Alt-Svc Julian Reschke
• alt-svc issue 58: Number of alternate services used Julian Reschke
• Fwd: Protocol Action: 'HTTP Digest Access Authentication' to Proposed Standard (draft-ietf-httpauth-digest-19.txt) Julian Reschke
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: can GET do for QUERY? extending Partial Content Julian Reschke
• Re: [Technical Errata Reported] RFC7231 (4351) Nico Williams
• Re: [Technical Errata Reported] RFC7231 (4351) Mark Nottingham

Wednesday, 29 April 2015

• Re: [Technical Errata Reported] RFC7231 (4351) Roy T. Fielding
• Re: [Technical Errata Reported] RFC7231 (4351) Nico Williams
• Re: [Technical Errata Reported] RFC7231 (4351) Roy T. Fielding
• Re: can GET do for QUERY? extending Partial Content Willy Tarreau
• Re: [Technical Errata Reported] RFC7231 (4351) Nico Williams
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: [Technical Errata Reported] RFC7231 (4351) Adrien de Croy
• Re: [Technical Errata Reported] RFC7231 (4351) Nico Williams
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Adrien de Croy
• Re: Bad link in RFC 7234 Will Sargent
• Re: Bad link in RFC 7234 Will Sargent
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Nico Williams
• Re: Bad link in RFC 7234 Tony Hansen
• [Technical Errata Reported] RFC7231 (4351) RFC Errata System
• Bad link in RFC 7234 Will Sargent
• Re: can GET do for QUERY? extending Partial Content Michael Sweet
• Re: can GET do for QUERY? extending Partial Content Julian Reschke
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update Zhong Yu
• Re: Proposed HTTP SEARCH method update Zhong Yu
• Re: can GET do for QUERY? extending Partial Content Zhong Yu
• Re: can GET do for QUERY? extending Partial Content Willy Tarreau
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: can GET do for QUERY? extending Partial Content Julian Reschke
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Wenbo Zhu
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Julian Reschke
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Roy T. Fielding
• Re: Proposed HTTP SEARCH method update Zhong Yu
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Nico Williams
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Nico Williams
• Re: can GET do for QUERY? extending Partial Content Willy Tarreau
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: can GET do for QUERY? extending Partial Content Willy Tarreau
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Zhong Yu
• Re: can GET do for QUERY? extending Partial Content Willy Tarreau
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: can GET do for QUERY? extending Partial Content Michael Sweet
• Re: can GET do for QUERY? extending Partial Content Julian Reschke
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: can GET do for QUERY? extending Partial Content Julian Reschke
• Re: can GET do for QUERY? extending Partial Content Julian Reschke
• Re: can GET do for QUERY? extending Partial Content Eric Covener
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: can GET do for QUERY? extending Partial Content Michael Sweet
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: can GET do for QUERY? extending Partial Content Willy Tarreau
• Re: can GET do for QUERY? extending Partial Content henry.story@bblfish.net
• Re: can GET do for QUERY? Willy Tarreau
• Re: can GET do for QUERY? Julian Reschke
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Amos Jeffries
• Re: *** GMX Spamverdacht *** Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Julian Reschke
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Willy Tarreau
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Adrien de Croy
• Re: can GET do for QUERY? Willy Tarreau
• Re: Clarification for RFC7231 CONNECT (section 4.3.6) Willy Tarreau
• Re: Clarification on HTTP caching (RFC 7234) Mark Nottingham
• Re: Clarification on HTTP caching (RFC 7234) Mark Nottingham

Tuesday, 28 April 2015

• Re: Clarification on HTTP caching (RFC 7234) Will Sargent
• Re: Clarification on HTTP caching (RFC 7234) Will Sargent
• Re: can GET do for QUERY? henry.story@bblfish.net
• can GET do for QUERY? henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Roy T. Fielding
• Clarification for RFC7231 CONNECT (section 4.3.6) Nico Williams
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Julian Reschke
• Clarification on HTTP caching (RFC 7234) Will Sargent
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Roy T. Fielding
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT henry.story@bblfish.net
• Re: An HTTP Status Code to Report Legal Obstacles and 451 Kari Hurtta
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Julian Reschke

Monday, 27 April 2015

• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT Julian Reschke
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT ashok malhotra
• Re: Proposed HTTP SEARCH method update - SEARCH is to GET what PATCH is to PUT ashok malhotra
• Re: Proposed HTTP SEARCH method update - QUERY is to GET what PATCH is to PUT henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update - SEARCH is to GET what PATCH is to PUT Roy T. Fielding
• Re: An HTTP Status Code to Report Legal Obstacles and 451 Roy T. Fielding
• timeouts in http/2 Stefan Eissing
• An HTTP Status Code to Report Legal Obstacles and 451 Kari Hurtta
• Re: Proposed HTTP SEARCH method update - SEARCH is to GET what PATCH is to PUT henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update - as partial representation Julian Reschke
• Re: Proposed HTTP SEARCH method update - as partial representation henry.story@bblfish.net
• IETF93 (Prague) Mark Nottingham

Sunday, 26 April 2015

• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update Ashok Malhotra
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update Ashok Malhotra
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update Amos Jeffries
• Re: Proposed HTTP SEARCH method update Amos Jeffries
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net

Saturday, 25 April 2015

• I-D Action: draft-ietf-httpbis-legally-restricted-status-00.txt internet-drafts@ietf.org
• Re: Proposed HTTP SEARCH method update James M Snell
• Re: Proposed HTTP SEARCH method update Mark Nottingham
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update Mark Nottingham
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net

Thursday, 23 April 2015

• Re: Do ALTSVC parameters need to have a value? Julian Reschke
• Re: Do ALTSVC parameters need to have a value? Roy T. Fielding
• Re: Do ALTSVC parameters need to have a value? Bence Béky
• Re: Do ALTSVC parameters need to have a value? Julian Reschke
• Do ALTSVC parameters need to have a value? Bence Béky

Wednesday, 22 April 2015

• Re: [Technical Errata Reported] RFC7230 (4189) Walter H.
• Re: [Technical Errata Reported] RFC7230 (4189) Willy Tarreau
• [Errata Held for Document Update] RFC7230 (4189) RFC Errata System
• Re: [Technical Errata Reported] RFC7230 (4189) Barry Leiba
• Re: [Technical Errata Reported] RFC7230 (4189) Zhong Yu
• Re: [Technical Errata Reported] RFC7230 (4189) Willy Tarreau

Tuesday, 21 April 2015

• Re: Proposed HTTP SEARCH method update James M Snell
• Re: Proposed HTTP SEARCH method update Mark Nottingham
• Re: Proposed HTTP SEARCH method update James M Snell
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: [Technical Errata Reported] RFC7230 (4189) Zhong Yu
• Re: [Technical Errata Reported] RFC7230 (4189) Zhong Yu
• Re: [Technical Errata Reported] RFC7230 (4189) Amos Jeffries
• Re: [Technical Errata Reported] RFC7230 (4189) Julian Reschke
• Re: [Technical Errata Reported] RFC7230 (4189) Julian Reschke

Monday, 20 April 2015

• Re: I-D Action: draft-ietf-httpbis-tunnel-protocol-03.txt Mark Nottingham
• Re: Proposed HTTP SEARCH method update Mark Baker

Saturday, 18 April 2015

• Re: Server Push used for long polling Anton Tveretin

Sunday, 19 April 2015

• Re: The ALPN Header Field Martin Thomson
• I-D Action: draft-ietf-httpbis-tunnel-protocol-03.txt internet-drafts@ietf.org

Saturday, 18 April 2015

• Re: The ALPN Header Field Mark Nottingham
• Re: Proposed HTTP SEARCH method update ashok malhotra
• Re: Results of calls for adoption Mark Nottingham
• Re: Results of calls for adoption Tim Bray
• Re: Results of calls for adoption Mark Nottingham
• Re: Results of calls for adoption Mark Nottingham
• Re: Results of calls for adoption Tim Bray
• Re: Results of calls for adoption Tim Bray

Friday, 17 April 2015

• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net
• Re: Proposed HTTP SEARCH method update Julian Reschke
• Re: Proposed HTTP SEARCH method update henry.story@bblfish.net

Thursday, 16 April 2015

• Library to Convert HTTP 2.0 to HTTP 1.1 Vimala Tadepalli
• Re: HTTP/2 and path fragments Zhong Yu
• Re: HTTP/2 and path fragments Simpson, Robby (GE Energy Management)
• Re: HTTP/2 and path fragments Daniel Stenberg
• HTTP/2 and path fragments Simpson, Robby (GE Energy Management)
• Re: The ALPN Header Field Willy Tarreau
• Re: The ALPN Header Field Amos Jeffries

Wednesday, 15 April 2015

• The ALPN Header Field Martin Thomson

Tuesday, 14 April 2015

• Re: 2 questions Martin Thomson
• Re: 2 questions Yoav Nir
• Re: [Errata Rejected] RFC7234 (4334) Julian Reschke
• Re: [Errata Rejected] RFC7234 (4334) Mark Nottingham
• Re: [Errata Rejected] RFC7234 (4334) Tony Hansen

Monday, 13 April 2015

• Re: [Errata Rejected] RFC7234 (4334) Mark Nottingham
• Protocol Action: 'The Hypertext Transfer Protocol (HTTP) Authentication-Info and Proxy- Authentication-Info Response Header Fields' to Proposed Standard (draft-ietf-httpbis-auth-info-05.txt) The IESG
• Re: 2 questions Martin Thomson
• Re: 2 questions Amos Jeffries
• Re: 2 questions Ilari Liusvaara
• Re: 2 questions Glen
• Re: 2 questions Glen
• Re: 2 questions Maxthon Chan
• [Errata Rejected] RFC7234 (4334) RFC Errata System
• [Editorial Errata Reported] RFC7234 (4334) RFC Errata System
• Re: 2 questions Amos Jeffries

Sunday, 12 April 2015

• Re: 2 questions Jim Manico
• Re: 2 questions Glen
• Re: 2 questions Glen
• I-D Action: draft-ietf-httpbis-cice-00.txt internet-drafts@ietf.org

Saturday, 11 April 2015

• Re: 2 questions Yoav Nir
• Re: 2 questions Jim Manico
• Re: 2 questions Glen
• Proposal for HTTP SEARCH Verb ashok malhotra

Friday, 10 April 2015

• Re: Proposed HTTP SEARCH method update James M Snell
• Re: Proposed HTTP SEARCH method update Yorkie Liu
• Re: Proposed HTTP SEARCH method update James M Snell
• Re: Proposed HTTP SEARCH method update Michael Sweet
• Proposed HTTP SEARCH method update James M Snell
• Re: 2 questions Ilari Liusvaara
• Re: Connection Reuse spec clarification Patrick McManus
• Connection Reuse spec clarification Samuel Giles
• Re: 2 questions ChanMaxthon
• Re: 2 questions Glen
• Re: 2 questions Roland Zink

Thursday, 9 April 2015

• Re: 2 questions Martin Thomson
• Re: 2 questions OSCAR GONZALEZ DE DIOS
• Re: 2 questions Martin Thomson
• Re: "Timeout" request header to tell server to wait for resource to become available Martin Thomson
• Re: 2 questions Benjamin Carlyle
• Re: "Timeout" request header to tell server to wait for resource to become available Benjamin Carlyle

Wednesday, 8 April 2015

• Re: Range Responses of Indeterminate Length: Draft Mark Nottingham
• Re: Overhead of HTTP/2 Stream Management. Walter H.
• Re: [Moderator Action] Range Responses of Indeterminate Length: Draft Rodger Combs
• Re: Range Responses of Indeterminate Length: Draft Mark Nottingham

Tuesday, 7 April 2015

• I-D Action: draft-ietf-httpbis-auth-info-05.txt internet-drafts@ietf.org
• Re: I-D ACTION:draft-ietf-httpbis-auth-info-04.txt Julian Reschke
• Re: [Moderator Action] Range Responses of Indeterminate Length: Draft Rodger Combs
• Re: Range Responses of Indeterminate Length: Draft Michael Sweet
• Re: [Moderator Action] Range Responses of Indeterminate Length: Draft Rodger Combs
• Re: [Moderator Action] Range Responses of Indeterminate Length: Draft Rodger Combs
• Re: Range Responses of Indeterminate Length: Draft Mark Nottingham
• Re: Range Responses of Indeterminate Length: Draft Mark Nottingham
• Re: Range Responses of Indeterminate Length: Draft Martin J. Dürst
• Re: Range Responses of Indeterminate Length: Draft Mark Nottingham
• Results of calls for adoption Mark Nottingham
• Re: RFC 7538 on The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect) Mark Nottingham

Monday, 6 April 2015

• Fwd: RFC 7538 on The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect) Julian Reschke
• Range Responses of Indeterminate Length: Draft Rodger Combs
• Re: Overhead of HTTP/2 Stream Management. Max Bruce
• Re: Overhead of HTTP/2 Stream Management. Max Bruce
• Re: Overhead of HTTP/2 Stream Management. Willy Tarreau

Sunday, 5 April 2015

• Re: Overhead of HTTP/2 Stream Management. Max Bruce
• Re: Overhead of HTTP/2 Stream Management. Max Bruce
• Re: Overhead of HTTP/2 Stream Management. Roberto Peon
• Re: Overhead of HTTP/2 Stream Management. Willy Tarreau
• Re: Overhead of HTTP/2 Stream Management. Max Bruce
• Re: Overhead of HTTP/2 Stream Management. Greg Wilkins
• Re: Overhead of HTTP/2 Stream Management. Max Bruce
• Re: Overhead of HTTP/2 Stream Management. Willy Tarreau
• Re: Overhead of HTTP/2 Stream Management. Max Bruce
• Re: Overhead of HTTP/2 Stream Management. Willy Tarreau
• Overhead of HTTP/2 Stream Management. Max Bruce
• Re: SNI requirement for H2 Greg Wilkins
• Re: Linking a cookie to an IP address is a very bad in 2015... Walter H.

Saturday, 4 April 2015

• Re: Linking a cookie to an IP address is a very bad in 2015... Eric Vyncke (evyncke)
• Re: Linking a cookie to an IP address is a very bad in 2015... Jim Manico
• Re: Linking a cookie to an IP address is a very bad in 2015... Max Bruce
• Re: Linking a cookie to an IP address is a very bad in 2015... Max Bruce
• Re: Linking a cookie to an IP address is a very bad in 2015... Jim Manico
• Re: Linking a cookie to an IP address is a very bad in 2015... Walter H.
• Re: Linking a cookie to an IP address is a very bad in 2015... Walter H.
• Re: Linking a cookie to an IP address is a very bad in 2015... Jim Manico
• Re: Linking a cookie to an IP address is a very bad in 2015... Eric Vyncke (evyncke)
• Re: Linking a cookie to an IP address is a very bad in 2015... Max Bruce
• Re: Linking a cookie to an IP address is a very bad in 2015... Walter H.
• Re: Alt-Svc + Proxy Pac Martin Thomson
• Re: SNI requirement for H2 Martin Thomson

Friday, 3 April 2015

• Re: Alt-Svc + Proxy Pac Ryan Hamilton
• Re: Alt-Svc + Proxy Pac Patrick McManus
• Re: Alt-Svc + Proxy Pac Ryan Hamilton
• Re: Alt-Svc + Proxy Pac Ryan Hamilton
• Re: Alt-Svc + Proxy Pac Ryan Hamilton
• Re: SNI requirement for H2 Willy Tarreau
• Re: SNI requirement for H2 Martin Thomson
• Re: SNI requirement for H2 Willy Tarreau
• Re: SNI requirement for H2 Roberto Peon
• SNI requirement for H2 Nicholas Hurley
• Re: Alt-Svc + Proxy Pac Patrick McManus
• Re: Alt-Svc + Proxy Pac Francesco Chemolli
• Re: Alt-Svc + Proxy Pac Martin Thomson
• Re: Alt-Svc + Proxy Pac Martin Thomson
• Alt-Svc + Proxy Pac Ryan Hamilton
• Re: Linking a cookie to an IP address is a very bad in 2015... Max Bruce
• Re: Linking a cookie to an IP address is a very bad in 2015... Walter H.
• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Re: Linking a cookie to an IP address is a very bad in 2015... Walter H.

Thursday, 2 April 2015

• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Re: Linking a cookie to an IP address is a very bad in 2015... Walter H.
• Re: Linking a cookie to an IP address is a very bad in 2015... Jim Manico
• Re: Linking a cookie to an IP address is a very bad in 2015... Jim Manico
• Re: Linking a cookie to an IP address is a very bad in 2015... Michael Sweet
• Re: Linking a cookie to an IP address is a very bad in 2015... Zhong Yu
• Re: Linking a cookie to an IP address is a very bad in 2015... Martin Thomson
• Re: Linking a cookie to an IP address is a very bad in 2015... Zhong Yu
• Re: Linking a cookie to an IP address is a very bad in 2015... Martin Thomson
• Re: Linking a cookie to an IP address is a very bad in 2015... Zhong Yu
• Re: Linking a cookie to an IP address is a very bad in 2015... Zhong Yu
• Re: Linking a cookie to an IP address is a very bad in 2015... Michael Sweet
• Re: Linking a cookie to an IP address is a very bad in 2015... Eric Vyncke (evyncke)
• Re: Linking a cookie to an IP address is a very bad in 2015... Eric Vyncke (evyncke)
• Re: h2 implementation list -- PLEASE UPDATE Mark Nottingham
• Re: How to reset ALTSVC Ryan Hamilton
• Re: h2 implementation list -- PLEASE UPDATE Greg Wilkins
• Re: h2 implementation list -- PLEASE UPDATE Mark Nottingham
• Re: h2 implementation list -- PLEASE UPDATE Martin Thomson
• Re: h2 implementation list -- PLEASE UPDATE Max Bruce
• Re: h2 implementation list -- PLEASE UPDATE Mark Nottingham
• h2 implementation list -- PLEASE UPDATE Mark Nottingham
• Re: How to reset ALTSVC Mark Nottingham

Wednesday, 1 April 2015

• Re: How to reset ALTSVC Ryan Hamilton
• Re: 2 questions Jason T. Greene
• Re: Linking a cookie to an IP address is a very bad in 2015... Jim Manico
• Re: 2 questions Ted Hardie
• Re: Linking a cookie to an IP address is a very bad in 2015... Michael Sweet
• Re: Linking a cookie to an IP address is a very bad in 2015... Michael Sweet
• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Re: Linking a cookie to an IP address is a very bad in 2015... Max Bruce
• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Re: Call for Adoption: draft-reschke-rfc54987bis Willy Tarreau
• Re: Call for Adoption: draft-reschke-rfc54987bis Willy Tarreau
• Re: Linking a cookie to an IP address is a very bad in 2015... Max Bruce
• Re: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Re: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Re: Call for Adoption: draft-reschke-rfc54987bis Willy Tarreau
• Re: Call for Adoption: draft-reschke-rfc54987bis Willy Tarreau
• Re: HTTP/2 in Apache Traffic Server (proxy server / cache) Stefan Eissing
• Re: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Re: 2 questions Simpson, Robby (GE Energy Management)
• Re: HTTP/2 in Apache Traffic Server (proxy server / cache) Simpson, Robby (GE Energy Management)
• Re: How to reset ALTSVC Martin Thomson
• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Re: Linking a cookie to an IP address is a very bad in 2015... Jim Manico
• Re: "Timeout" request header to tell server to wait for resource to become available Brendan Long
• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Re: Linking a cookie to an IP address is a very bad in 2015... Michael Sweet
• Re: Call for Adoption: draft-reschke-rfc54987bis squid3@treenet.co.nz
• Re: How to reset ALTSVC Bence Béky
• Re: Linking a cookie to an IP address is a very bad in 2015... Eric Vyncke (evyncke)
• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Re: Linking a cookie to an IP address is a very bad in 2015... Willy Tarreau
• Linking a cookie to an IP address is a very bad in 2015... Eric Vyncke (evyncke)
• Preliminary minutes for Dallas Mark Nottingham
• Re: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Re: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Re: Call for Adoption: draft-reschke-rfc54987bis Julian Reschke
• Re: HTTP/2 in Apache Traffic Server (proxy server / cache) Cory Benfield
• Re: Call for Adoption: draft-reschke-rfc54987bis Cory Benfield
• Re: 2 questions Maxthon Chan
• Re: 2 questions Poul-Henning Kamp
• Re: 2 questions Yoav Nir
• Re: 2 questions Amos Jeffries
• Re: HTTP/2 in Apache Traffic Server (proxy server / cache) Mark Nottingham
• Re: 2 questions ChanMaxthon
• Re: HTTP/2 in Apache Traffic Server (proxy server / cache) Amos Jeffries
• Re: Header addition with HTTP 2.0 Amos Jeffries
• Re: How to reset ALTSVC Ryan Hamilton
• Re: comprehensive TLS is not the solution, it's a bug ... (was 2 questions) Amos Jeffries
• Re: comprehensive TLS is not the solution, it's a bug ... (was 2 questions) Amos Jeffries
• Re: Call for Adoption: draft-reschke-rfc54987bis Amos Jeffries
• Re: "Timeout" request header to tell server to wait for resource to become available Mark Nottingham

Last message date: Tuesday, 30 June 2015 08:08:23 UTC