ietf-http-wg@w3.org from October to December 2010 by author

, Tue@colossus.hpl.hp.com, 21@colossus.hpl.hp.com, Dec@colossus.hpl.hp.com, 2010@colossus.hpl.hp.com, "11:24:20"@colossus.hpl.hp.com, -0300@colossus.hpl.hp.com

• Ликвидация предприятий (по всей Украине ) (Tuesday, 21 December)

=JeffH

• fyi: draft-ietf-httpstate-cookie-15.txt (Thursday, 21 October)

Adam Barth

• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Tuesday, 14 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Re: Content-Disposition next steps (Monday, 13 December)
• Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 12 December)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 12 December)
• Re: TICKET 259: 'treat as invalid' not defined (Saturday, 11 December)
• Re: TICKET 259: 'treat as invalid' not defined (Saturday, 11 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 8 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: Content-Disposition next steps (Saturday, 4 December)
• Re: Content-Disposition next steps (Saturday, 4 December)
• Re: Content-Disposition next steps (Friday, 3 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Friday, 26 November)
• Re: Content-Disposition next steps (Tuesday, 9 November)
• Re: TICKET 259: 'treat as invalid' not defined (Monday, 8 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Sunday, 7 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: issue 264: language tagging, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: issue 258, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Ticket 260: multiple disposition types, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Ticket 262: Discuss whether percent-decoding should also be done by receivers. (Tuesday, 2 November)
• TICKET 259: 'treat as invalid' not defined (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: #250 / #251 (connect bodies) (Friday, 29 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Wednesday, 27 October)
• Re: fyi: draft-ietf-httpstate-cookie-15.txt (Thursday, 21 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: [#95] Multiple Content-Lengths (Monday, 11 October)
• Re: [#95] Multiple Content-Lengths (Friday, 8 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: %encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: %encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• %encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)

Adrian Chadd

• Re: #250 / #251 (connect bodies) (Friday, 29 October)

Adrien de Croy

• Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation (Sunday, 19 December)
• Re: [websec] [apps-discuss] [kitten] [saag] HTTP authentication: the next generation (Sunday, 19 December)
• Re: [kitten] [apps-discuss] [saag] HTTP authentication: the next generation (Monday, 13 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: Headers-Not-Recognized for HTTP (Monday, 22 November)
• WWW-Authenticate / Proxy-Authenticate with 200 response (Thursday, 18 November)
• Re: API Rate Limits and HTTP Code [#255] (Saturday, 13 November)
• Re: TICKET 259: 'treat as invalid' not defined (Tuesday, 9 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: Issue 240: Migrate Upgrade details from RFC2817 (Saturday, 30 October)
• Re: Proposal: 205 Bodies [#88] (Monday, 25 October)
• Re: Proposal: 205 Bodies [#88] (Monday, 25 October)
• Re: chunk-extensions (Friday, 22 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)

Alexey Melnikov

• Re: [kitten] [saag] HTTP authentication: the next generation (Sunday, 12 December)
• Re: [kitten] [saag] HTTP authentication: the next generation (Sunday, 12 December)
• Re: I-D Action:draft-ietf-httpbis-authscheme-registrations-00.txt (Friday, 10 December)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Sunday, 17 October)

Anne van Kesteren

• Re: Same Origin Policy and HTTP Authentication (Tuesday, 7 December)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: Issue 160 (Redirects and non-GET methods) (Friday, 1 October)

Anthony Bryan

• Re: draft-bryan-metalinkhttp-18.txt (Tuesday, 23 November)

Ben Laurie

• Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation (Monday, 20 December)
• Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation (Sunday, 19 December)
• Re: [websec] [saag] HTTP authentication: the next generation (Monday, 13 December)

Ben Niven-Jenkins

• Re: [AVT] Fw: [httpstreaming] Agenda and Slides (Sunday, 7 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)

Bjoern Hoehrmann

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: I-D Action:draft-ietf-httpbis-authscheme-registrations-00.txt (Thursday, 9 December)
• Re: Multiple Realm Authentication? (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: Same Origin Policy and HTTP Authentication (Thursday, 9 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: TICKET 259: 'treat as invalid' not defined (Monday, 8 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Sunday, 7 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Friday, 5 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: Issue 248: client "Date" requirements (Monday, 11 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)

Brian Pane

• Pipelining hinting (Thursday, 16 December)

Bryce Nesbitt

• Re: API Rate Limits and HTTP Code [#255] (Thursday, 11 November)

Carsten Bormann

• Re: [kitten] [apps-discuss] [saag] HTTP authentication: the next generation (Monday, 13 December)

Chirag Shah

• Same Origin Policy and HTTP Authentication (Sunday, 5 December)

Collin Jackson

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)

Cullen Jennings

• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)

Dan Winship

• Re: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)

Daniel Stenberg

• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)
• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)
• Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call) (Thursday, 16 December)
• Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call) (Thursday, 16 December)
• Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call) (Wednesday, 15 December)
• Re: Proposal: 205 Bodies [#88] (Monday, 25 October)
• Re: chunk-extensions (Friday, 22 October)
• Re: chunk-extensions (Friday, 22 October)
• Re: chunk-extensions (Friday, 22 October)
• Re: Issue 248: client "Date" requirements (Monday, 18 October)
• Re: Date format glitch (Monday, 11 October)
• Date format glitch (Sunday, 10 October)

Dave Cridland

• Re: [apps-discuss] [kitten] [saag] HTTP authentication: the next generation (Monday, 13 December)
• Re: [kitten] [apps-discuss] [saag] HTTP authentication: the next generation (Monday, 13 December)
• Re: [kitten] [apps-discuss] [saag] HTTP authentication: the next generation (Monday, 13 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)

Dave Raggett

• Re: [apps-discuss] [kitten] [saag] HTTP authentication: the next generation (Monday, 13 December)

David Booth

• Re: Comments on Section 6.1 (Monday, 8 November)
• Comments on Section 6.1 (Saturday, 6 November)

David Morris

• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)

der Mouse

• Re: [saag] [websec] [kitten] [apps-discuss] HTTP authentication: the next generation (Thursday, 16 December)

Eric J. Bowman

• Re: workability (or otherwise) of HTTP upgrade (Tuesday, 30 November)
• Re: workability (or otherwise) of HTTP upgrade (Tuesday, 30 November)
• Re: workability (or otherwise) of HTTP upgrade (Tuesday, 30 November)
• Re: workability (or otherwise) of HTTP upgrade (Friday, 26 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Friday, 5 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)
• Re: API Rate Limits and HTTP Code [#255] (Friday, 29 October)
• Re: chunk-extensions (Saturday, 23 October)
• Re: #230: Considerations for registering new methods (Wednesday, 20 October)
• Re: #230: Considerations for registering new methods (Wednesday, 20 October)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Fwd: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Friday, 15 October)
• Re: [#95] Multiple Content-Lengths (Friday, 15 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)

Greg Wilkins

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 8 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)
• Re: workability (or otherwise) of HTTP upgrade (Friday, 26 November)
• workability (or otherwise) of HTTP upgrade (Friday, 26 November)

Henrik Nordström

• Re: [#193] Trailers and intermediaries (Saturday, 23 October)

Herbert van de Sompel

• Memento Internet Draft (Friday, 12 November)
• Re: Extending redirects to suggest updated locations ? (Monday, 4 October)

Ian Hickson

• Re: Comments on draft-ietf-httpbis-content-disp (Monday, 1 November)

Internet-Drafts@ietf.org

• I-D Action:draft-ietf-httpbis-content-disp-04.txt (Friday, 12 November)
• I-D Action:draft-ietf-httpbis-authscheme-registrations-00.txt (Tuesday, 9 November)
• I-D Action:draft-ietf-httpbis-p7-auth-12.txt (Monday, 25 October)
• I-D Action:draft-ietf-httpbis-p5-range-12.txt (Monday, 25 October)
• I-D Action:draft-ietf-httpbis-p6-cache-12.txt (Monday, 25 October)
• I-D Action:draft-ietf-httpbis-p4-conditional-12.txt (Monday, 25 October)
• I-D Action:draft-ietf-httpbis-p2-semantics-12.txt (Monday, 25 October)
• I-D Action:draft-ietf-httpbis-content-disp-03.txt (Monday, 25 October)
• I-D Action:draft-ietf-httpbis-p1-messaging-12.txt (Monday, 25 October)
• I-D Action:draft-ietf-httpbis-p3-payload-12.txt (Monday, 25 October)

Jack Moffitt

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)

Jamie Lokier

• Re: workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)

Joe Mason

• RE: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)

John C Klensin

• Re: [saag] [apps-discuss] [websec] [kitten] HTTP authentication: the next generation (Friday, 17 December)
• Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation (Tuesday, 14 December)

John Tamplin

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)

Juan M. Sierra Lebrón

• RE: #250 / #251 (connect bodies) (Friday, 29 October)
• RE: API Rate Limits and HTTP Code [#255] (Friday, 29 October)
• RE: API Rate Limits and HTTP Code [#255] (Friday, 29 October)
• RE: #250 / #251 (connect bodies) (Friday, 29 October)

Julian Reschke

• Re: Content-Disposition next steps (Tuesday, 21 December)
• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)
• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)
• Re: Content-Disposition next steps (Friday, 17 December)
• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Content-Disposition next steps (Wednesday, 15 December)
• Re: Content-Disposition next steps (Wednesday, 15 December)
• Re: Fwd: Content-Disposition and IE (Tuesday, 14 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Tuesday, 14 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Re: Fwd: Content-Disposition and IE (Monday, 13 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Re: [websec] HTTP authentication: the next generation (Monday, 13 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Fwd: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Monday, 13 December)
• Re: Content-Disposition next steps (Monday, 13 December)
• Re: TICKET 259: 'treat as invalid' not defined (Monday, 13 December)
• Re: Content-Disposition next steps (Monday, 13 December)
• Re: TICKET 259: 'treat as invalid' not defined (Monday, 13 December)
• Re: TICKET 259: 'treat as invalid' not defined (Saturday, 11 December)
• Re: I-D Action:draft-ietf-httpbis-authscheme-registrations-00.txt (Friday, 10 December)
• Re: TICKET 259: 'treat as invalid' not defined (Friday, 10 December)
• Re: TAG resolution on redirection with fragment identifiers (Friday, 10 December)
• Re: I-D Action:draft-ietf-httpbis-authscheme-registrations-00.txt (Thursday, 9 December)
• Re: TAG resolution on redirection with fragment identifiers (Sunday, 5 December)
• Re: Content-Disposition next steps (Saturday, 4 December)
• Re: Content-Disposition next steps (Saturday, 4 December)
• Re: Content-Disposition next steps (Saturday, 4 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: workability (or otherwise) of HTTP upgrade (Tuesday, 30 November)
• Re: workability (or otherwise) of HTTP upgrade (Friday, 26 November)
• Re: draft-yevstifeyev-http-headers-not-recognized-01.txt (Tuesday, 23 November)
• Re: Headers-Not-Recognized for HTTP (Tuesday, 23 November)
• Re: Please Review my Internet-Draft (Monday, 22 November)
• Re: Please Review my Internet-Draft (Monday, 22 November)
• Re: WWW-Authenticate / Proxy-Authenticate with 200 response (Thursday, 18 November)
• Re: API Rate Limits and HTTP Code [#255] (Saturday, 13 November)
• Re: I-D Action:draft-ietf-httpbis-content-disp-04.txt (Friday, 12 November)
• Re: TICKET 259: 'treat as invalid' not defined (Friday, 12 November)
• Re: Content-Disposition next steps (Thursday, 11 November)
• Re: TICKET 259: 'treat as invalid' not defined (Tuesday, 9 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 9 November)
• Re: Ticket 260: multiple disposition types, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 9 November)
• Re: Ticket 262: Discuss whether percent-decoding should also be done by receivers. (Tuesday, 9 November)
• Re: Content-Disposition next steps (Tuesday, 9 November)
• Re: TICKET 259: 'treat as invalid' not defined (Monday, 8 November)
• Re: TICKET 259: 'treat as invalid' not defined (Monday, 8 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 7 November)
• Re: Content-Location on 200 responses (Sunday, 7 November)
• Re: Identifying the Resource Associated with a Representation? (Sunday, 7 November)
• Re: Comments on Section 6.1 (Sunday, 7 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Content-Disposition next steps (Sunday, 7 November)
• P7: IANA registry for schemes (issue 141) (Sunday, 7 November)
• Re: #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)
• Issue 265: Clarify that C-D spec does not apply to multipart upload (Thursday, 4 November)
• Issue 263 (text about historical percent-decoding unclear), was: Comments on draft-ietf-httpbis-content-disp (Thursday, 4 November)
• Re: issue 264: language tagging, was: Comments on draft-ietf-httpbis-content-disp (Wednesday, 3 November)
• Re: Ticket 262: Discuss whether percent-decoding should also be done by receivers. (Wednesday, 3 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• issue 264: language tagging, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• issue 258, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Ticket 260: multiple disposition types, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• language tag support, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Ticket 260: multiple disposition types, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Issue 240: Migrate Upgrade details from RFC2817 (Sunday, 31 October)
• Re: Issue 240: Migrate Upgrade details from RFC2817 (Saturday, 30 October)
• Re: [#203] Max-forwards and extension methods (Saturday, 30 October)
• Issue 240: Migrate Upgrade details from RFC2817 (Thursday, 28 October)
• Call for feedback: HTML application cache (Thursday, 28 October)
• Re: issue 226, "proxies not supporting certain methods" (Thursday, 28 October)
• Re: issue 226, "proxies not supporting certain methods" (Wednesday, 27 October)
• Re: Proposal: 205 Bodies [#88] (Tuesday, 26 October)
• #251 (connect bodies), was: Proposal: 205 Bodies [#88] (Tuesday, 26 October)
• Re: [#203] Max-forwards and extension methods (Monday, 25 October)
• Re: Proposal: 205 Bodies [#88] (Monday, 25 October)
• httpbis -12 drafts (Monday, 25 October)
• Re: I-D Action:draft-ietf-httpbis-content-disp-03.txt (Monday, 25 October)
• Re: #233: Is * usable as a request-uri for new methods? (Saturday, 23 October)
• Re: [#193] Trailers and intermediaries (Saturday, 23 October)
• Re: #233: Is * usable as a request-uri for new methods? (Friday, 22 October)
• Re: Issue 248: client "Date" requirements (Friday, 22 October)
• Re: [#193] Trailers and intermediaries (Friday, 22 October)
• Re: Issue 245 (percent escaping), was: Working Group Last Call: Content-Disposition (Friday, 22 October)
• Re: #230: Considerations for registering new methods (Thursday, 21 October)
• Re: Issue 248: client "Date" requirements (Thursday, 21 October)
• Re: #233: Is * usable as a request-uri for new methods? (Thursday, 21 October)
• Issue 244 (repeated parameters), was: Working Group Last Call: Content-Disposition (Thursday, 21 October)
• Issue 245 (percent escaping), was: Working Group Last Call: Content-Disposition (Thursday, 21 October)
• Re: #230: Considerations for registering new methods (Wednesday, 20 October)
• Re: Content Auto-negotiation (Tuesday, 19 October)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 19 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Monday, 18 October)
• Working Group Last Call: Content-Disposition (Sunday, 17 October)
• Re: [#95] Multiple Content-Lengths (Friday, 15 October)
• Re: [#95] Multiple Content-Lengths (Thursday, 14 October)
• Re: [#95] Multiple Content-Lengths (Thursday, 14 October)
• Re: LINK/UNLINK (Wednesday, 13 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: Issue 248: client "Date" requirements (Tuesday, 12 October)
• Re: Which headers to apply from a PUT request (Link?) (Tuesday, 12 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Tuesday, 12 October)
• Re: Issue 248: client "Date" requirements (Monday, 11 October)
• Issue 248: client "Date" requirements (Monday, 11 October)
• Making 307 redirects permantent, Re: Issue 160 (Redirects and non-GET methods) (Monday, 11 October)
• Re: Date format glitch (Monday, 11 October)
• Re: [#95] Multiple Content-Lengths (Monday, 11 October)
• Re: Date format glitch (Monday, 11 October)
• Re: Issue 141: "should we have an auth scheme registry" (Thursday, 7 October)
• Re: detecting support for percent encoding in C-D, was: repeated filename parameters (Tuesday, 5 October)
• Re: detecting support for percent encoding in C-D, was: repeated filename parameters (Monday, 4 October)
• detecting support for percent encoding in C-D, was: repeated filename parameters (Monday, 4 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Monday, 4 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: The robustness principle, as view by user agent implementors (Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02) (Sunday, 3 October)
• Re: %encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: %encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• %encoding in filename parameters. Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• treating invalid parameters in Content-Disposition (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Sunday, 3 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• repeated filename parameters, Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Re: "refresh" header (Saturday, 2 October)
• "refresh" header (Saturday, 2 October)
• Re: WGLC for draft-ietf-httpbis-content-disp ? (Friday, 1 October)
• Re: Issue 160 (Redirects and non-GET methods) (Friday, 1 October)

Karl Dubost

• Re: API Rate Limits and HTTP Code [#255] (Saturday, 13 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• API Rate Limits and HTTP Code (Thursday, 28 October)

Maciej Stachowiak

• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Monday, 13 December)
• Re: Content-Disposition next steps (Monday, 13 December)
• Re: Content-Disposition next steps (Monday, 13 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Monday, 6 December)
• Re: Content-Disposition next steps (Thursday, 11 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Friday, 5 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)
• Re: [#95] Multiple Content-Lengths (Tuesday, 19 October)
• Re: [#95] Multiple Content-Lengths (Friday, 15 October)
• Re: [#95] Multiple Content-Lengths (Friday, 15 October)
• Re: [#95] Multiple Content-Lengths (Friday, 8 October)

Mark Nottingham

• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: LC comments on draft-yevstifeyev-http-headers-not-recognized-08.txt (Tuesday, 14 December)
• LC comments on draft-yevstifeyev-http-headers-not-recognized-08.txt (Tuesday, 14 December)
• Fwd: Content-Disposition and IE (Monday, 13 December)
• Fwd: [websec] request for feedback on adoption of drafts to WG - until Dec-16 (Monday, 13 December)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 12 December)
• Re: TICKET 259: 'treat as invalid' not defined (Sunday, 12 December)
• Re: [apps-discuss] HTTP authentication: the next generation (Friday, 10 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 9 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 8 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: Content-Disposition next steps (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Monday, 6 December)
• Re: Same Origin Policy and HTTP Authentication (Monday, 6 December)
• Re: WWW-Authenticate / Proxy-Authenticate with 200 response (Monday, 6 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Monday, 6 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Monday, 6 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Thursday, 2 December)
• Re: Content-Disposition next steps (Wednesday, 1 December)
• Re: Ticket 262: Discuss whether percent-decoding should also be done by receivers. (Friday, 12 November)
• Re: TICKET 259: 'treat as invalid' not defined (Friday, 12 November)
• Re: Content-Disposition next steps (Friday, 12 November)
• Re: Content-Disposition next steps (Friday, 12 November)
• Re: API Rate Limits and HTTP Code [#255] (Friday, 12 November)
• Re: Identifying the Resource Associated with a Representation? (Tuesday, 9 November)
• Re: Identifying the Resource Associated with a Representation? (Tuesday, 9 November)
• Re: TICKET 259: 'treat as invalid' not defined (Tuesday, 9 November)
• Re: Comments on Section 6.1 (Tuesday, 9 November)
• Re: TICKET 259: 'treat as invalid' not defined (Tuesday, 9 November)
• Re: Ticket 260: multiple disposition types, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 9 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Tuesday, 9 November)
• Re: Ticket 262: Discuss whether percent-decoding should also be done by receivers. (Tuesday, 9 November)
• Re: Content-Disposition next steps (Tuesday, 9 November)
• Re: P7: IANA registry for schemes (issue 141) (Tuesday, 9 November)
• Re: Identifying the Resource Associated with a Representation? (Tuesday, 9 November)
• #243: iso-8859-1 in C-D (Sunday, 7 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Saturday, 6 November)
• Re: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)
• [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)
• Fwd: I-D Action:draft-zong-httpstreaming-gap-analysis-01.txt (Wednesday, 3 November)
• Re: Ticket 262: Discuss whether percent-decoding should also be done by receivers. (Wednesday, 3 November)
• Re: Issue 261: Check for requirements backing test cases, was: Comments on draft-ietf-httpbis-content-disp (Wednesday, 3 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)
• Re: #250 / #251 (connect bodies) (Friday, 29 October)
• Fwd: RFC 5988 on Web Linking (Friday, 29 October)
• Re: API Rate Limits and HTTP Code [#255] (Friday, 29 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: issue 226, "proxies not supporting certain methods" (Wednesday, 27 October)
• Re: #250 / #251 (connect bodies) (Wednesday, 27 October)
• Re: Proposal: 205 Bodies [#88] (Monday, 25 October)
• Re: chunk-extensions (Saturday, 23 October)
• Re: #233: Is * usable as a request-uri for new methods? (Friday, 22 October)
• Re: [#193] Trailers and intermediaries (Friday, 22 October)
• Re: [#193] Trailers and intermediaries (Friday, 22 October)
• chunk-extensions (Friday, 22 October)
• Re: NEW: #225: PUT and DELETE invalidation vs. staleness (Friday, 22 October)
• Re: #230: Considerations for registering new methods (Friday, 22 October)
• Re: ticket #78 (Relationship between 401, Authorization and WWW-Authenticate) (Thursday, 21 October)
• Re: #233: Is * usable as a request-uri for new methods? (Thursday, 21 October)
• Re: Issue 248: client "Date" requirements (Thursday, 21 October)
• Re: #230: Considerations for registering new methods (Wednesday, 20 October)
• Re: #230: Considerations for registering new methods (Wednesday, 20 October)
• Re: [#95] Multiple Content-Lengths (Wednesday, 20 October)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 19 October)
• #233: Is * usable as a request-uri for new methods? (Tuesday, 19 October)
• #229: Considerations for registering new status codes (Tuesday, 19 October)
• #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: NEW: #235: Cache Invalidation only happens upon successful responses (Tuesday, 19 October)
• Re: NEW: #235: Cache Invalidation only happens upon successful responses (Tuesday, 19 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 19 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Monday, 18 October)
• Re: Issue 248: client "Date" requirements (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: NEW: #235: Cache Invalidation only happens upon successful responses (Monday, 18 October)
• Re: CONNECT command with message body (Monday, 18 October)
• Re: NEW ISSUE: message-body in CONNECT response (Monday, 18 October)
• Re: [#177] Realm required on challenges (Monday, 18 October)
• Re: Does no-store in request imply no-cache? [#249] (Monday, 18 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Re: Does no-store in request imply no-cache? (Monday, 18 October)
• Fwd: Does no-store in request imply no-cache? (Sunday, 17 October)
• Re: [#95] Multiple Content-Lengths (Monday, 11 October)
• Content-Disposition (Sunday, 3 October)
• Re: "refresh" header (Sunday, 3 October)
• Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Working Group Last Call: draft-ietf-httpbis-content-disp-02 (Saturday, 2 October)
• Fwd: [apps-discuss] Fwd: WG Review: Web Security (websec) (Saturday, 2 October)
• WGLC for draft-ietf-httpbis-content-disp ? (Friday, 1 October)

Marsh Ray

• Re: [websec] [saag] [apps-discuss] [kitten] HTTP authentication: the next generation (Sunday, 19 December)

Martin J. Dürst

• Re: Fwd: Content-Disposition and IE (Tuesday, 14 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Tuesday, 14 December)
• Re: Updated Content-Disposition error handling proposal on the wiki (Tuesday, 14 December)
• Re: Comments on draft-ietf-httpbis-content-disp (Tuesday, 2 November)

Michael Chan

• 1st CFP: IJCAI-11 Workshop on Discovering Meaning On the Go in Large & Heterogeneous Data (LHD-11) (Saturday, 18 December)

mike amundsen

• Re: Headers-Not-Recognized for HTTP (Tuesday, 23 November)

Mike Kelly

• Re: Identifying the Resource Associated with a Representation? (Tuesday, 9 November)
• Re: Identifying the Resource Associated with a Representation? (Tuesday, 9 November)
• Re: Content-Location on 200 responses (Sunday, 7 November)
• Re: Identifying the Resource Associated with a Representation? (Sunday, 7 November)
• Content-Location on 200 responses (Friday, 5 November)

Moore, Jonathan

• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)

Mykyta Yevstifeyev

• First part of LC for draft-yevstifeyev-http-headers-not-recognized summary (Friday, 31 December)
• Last Call on draft-yevstifeyev-http-headers-not-recognized - summarizing first week (Wednesday, 22 December)
• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)
• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)
• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)
• Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call) (Thursday, 16 December)
• Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call) (Thursday, 16 December)
• Re: The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call) (Thursday, 16 December)
• The new version of draft-yevstifeyev-http-headers-not-recognized (Last Call) (Wednesday, 15 December)
• Re: LC comments on draft-yevstifeyev-http-headers-not-recognized-08.txt (Wednesday, 15 December)
• Re: LC comments on draft-yevstifeyev-http-headers-not-recognized-08.txt (Tuesday, 14 December)
• Re: draft-yevstifeyev-http-headers-not-recognized-01.txt (Tuesday, 23 November)
• Re: draft-yevstifeyev-http-headers-not-recognized-01.txt (Tuesday, 23 November)
• draft-yevstifeyev-http-headers-not-recognized-01.txt (Tuesday, 23 November)
• Headers-Not-Recognized for HTTP (was: Please review my Internet-Draft) (Monday, 22 November)
• Re: Please Review my Internet-Draft (Monday, 22 November)
• Re: Please Review my Internet-Draft (Monday, 22 November)
• Re: Please Review my Internet-Draft (Monday, 22 November)
• Please Review my Internet-Draft (Monday, 22 November)

Nathan

• Re: [websec] [apps-discuss] [kitten] [saag] HTTP authentication: the next generation (Sunday, 19 December)
• Re: Content-Location on 200 responses (Saturday, 6 November)
• Identifying the Resource Associated with a Representation? (Saturday, 6 November)
• Re: LINK/UNLINK (Wednesday, 13 October)
• LINK/UNLINK (Tuesday, 12 October)
• Which headers to apply from a PUT request (Link?) (Monday, 11 October)

Nicolas Alvarez

• Re: Issue 245 (percent escaping), was: Working Group Last Call: Content-Disposition (Friday, 22 October)

Ning Zong

• link for subscribing HTTP streaming mailing list (Wednesday, 10 November)
• RE: I-D Action:draft-zong-httpstreaming-gap-analysis-01.txt (Thursday, 4 November)

Noah Mendelsohn

• Re: TAG resolution on redirection with fragment identifiers (Sunday, 5 December)
• TAG resolution on redirection with fragment identifiers (Tuesday, 30 November)

Paul Hoffman

• Re: [saag] HTTP authentication: the next generation (Friday, 10 December)

Peter Saint-Andre

• HTTP authentication: the next generation (Friday, 10 December)
• Fwd: Last Call: <draft-ietf-httpstate-cookie-18.txt> (HTTP State Management Mechanism) to Proposed Standard (Thursday, 18 November)
• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 18 October)

Phillip Hallam-Baker

• Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation (Wednesday, 22 December)
• Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation (Wednesday, 22 December)
• Re: [websec] [apps-discuss] [kitten] [saag] HTTP authentication: the next generation (Saturday, 18 December)

Qin Wu

• Re: [AVT] Fw: [httpstreaming] Agenda and Slides (Monday, 8 November)
• Meeting room change for HTTP streaming Bar BOF (Sunday, 7 November)
• Fw: [httpstreaming] Agenda and Slides (Sunday, 7 November)
• Fw: [httpstreaming] Time and location for HTTP streaming bar BoF (Thursday, 4 November)

Richard L. Barnes

• Re: [saag] [http-auth] [websec] [kitten] HTTP authentication: the next generation (Monday, 13 December)

Robert Brewer

• RE: Issue 248: client "Date" requirements (Monday, 11 October)

Robert Sanderson

• Re: Please Review my Internet-Draft (Monday, 22 November)

Roy T. Fielding

• Re: [kitten] [saag] HTTP authentication: the next generation (Sunday, 12 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Thursday, 2 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)
• Re: Content Auto-negotiation (Tuesday, 19 October)
• Re: NEW: #235: Cache Invalidation only happens upon successful responses (Tuesday, 19 October)
• Re: NEW: #235: Cache Invalidation only happens upon successful responses (Monday, 18 October)

Stephen Farrell

• Re: [http-auth] [saag] [websec] [kitten] HTTP authentication: the next generation (Monday, 13 December)

Steven Bellovin

• Re: [saag] [websec] [kitten] [apps-discuss] HTTP authentication: the next generation (Monday, 13 December)

Sylvain Hellegouarch

• Re: draft-yevstifeyev-http-headers-not-recognized-01.txt (Tuesday, 23 November)
• Re: draft-yevstifeyev-http-headers-not-recognized-01.txt (Tuesday, 23 November)
• Re: draft-yevstifeyev-http-headers-not-recognized-01.txt (Tuesday, 23 November)
• Re: Headers-Not-Recognized for HTTP (was: Please review my Internet-Draft) (Monday, 22 November)

Thomas Broyer

• Re: "refresh" header (Saturday, 2 October)
• Re: I-D Action:draft-nottingham-http-portal-01.txt (Friday, 1 October)

Thomson, Martin

• RE: [#259] Handling invalid Content-Dispostion headers (Thursday, 4 November)

Tim Morgan

• Re: [http-auth] [websec] HTTP authentication: the next generation (Tuesday, 14 December)
• Re: [apps-discuss] [kitten] [saag] HTTP authentication: the next generation (Monday, 13 December)

Tony Hansen

• Re: Last Call: <draft-yevstifeyev-http-headers-not-recognized-08.txt> ('Headers-Not-Recognized' HTTP Header Field) to Experimental RFC (Friday, 17 December)

William A. Rowe Jr.

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Wednesday, 8 December)
• Re: workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)
• Re: workability (or otherwise) of HTTP upgrade (Wednesday, 1 December)
• Re: #250 / #251 (connect bodies) (Wednesday, 27 October)
• Re: [#95] Multiple Content-Lengths (Wednesday, 13 October)
• Re: detecting support for percent encoding in C-D, was: repeated filename parameters (Monday, 4 October)

William Waites

• Content Auto-negotiation (Tuesday, 19 October)

Willy Tarreau

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)
• Re: API Rate Limits and HTTP Code [#255] (Saturday, 13 November)
• Re: API Rate Limits and HTTP Code [#255] (Saturday, 13 November)
• Re: #250 / #251 (connect bodies) (Friday, 29 October)
• Re: API Rate Limits and HTTP Code [#255] (Friday, 29 October)
• Re: #250 / #251 (connect bodies) (Friday, 29 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Thursday, 28 October)
• Re: #250 / #251 (connect bodies) (Wednesday, 27 October)
• Re: Proposal: 205 Bodies [#88] (Tuesday, 26 October)
• Re: Proposal: 205 Bodies [#88] (Tuesday, 26 October)
• Re: chunk-extensions (Friday, 22 October)
• Re: fyi: draft-ietf-httpstate-cookie-15.txt (Thursday, 21 October)
• Re: fyi: draft-ietf-httpstate-cookie-15.txt (Thursday, 21 October)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: #230: Considerations for registering new methods (Tuesday, 19 October)
• Re: [#95] Multiple Content-Lengths (Monday, 18 October)
• Re: CONNECT command with message body (Monday, 18 October)
• Re: [#95] Multiple Content-Lengths (Thursday, 14 October)
• Re: [#95] Multiple Content-Lengths (Wednesday, 13 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: [#95] Multiple Content-Lengths (Tuesday, 12 October)
• Re: [#95] Multiple Content-Lengths (Friday, 8 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Re: Extending redirects to suggest updated locations ? (Sunday, 3 October)
• Extending redirects to suggest updated locations ? (Sunday, 3 October)

Yutaka OIWA

• Re: [http-auth] [websec] [kitten] [saag] HTTP authentication: the next generation (Tuesday, 14 December)
• Re: WWW-Authenticate / Proxy-Authenticate with 200 response (Thursday, 9 December)

Yves Lafon

• Re: TAG resolution on redirection with fragment identifiers (Monday, 13 December)

Zhi-Qiang Lei

• Multiple Realm Authentication? (Thursday, 18 November)

Zhong Yu

• Re: [hybi] workability (or otherwise) of HTTP upgrade (Tuesday, 7 December)

蓋文彼德斯

• Re: Unifying & standardizing X-Moz & X-Purpose headers (Monday, 11 October)

陈智昌

• Re: [#95] Multiple Content-Lengths (Wednesday, 13 October)
• Re: [#95] Multiple Content-Lengths (Monday, 11 October)
• Re: [#95] Multiple Content-Lengths (Friday, 8 October)

신정식, 申政湜

• Re: Content-Disposition next steps (Tuesday, 21 December)
• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Content-Disposition next steps (Thursday, 16 December)
• Re: Content-Disposition next steps (Wednesday, 15 December)

Last message date: Friday, 31 December 2010 06:12:45 UTC