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

=JeffH

• fya: Flickr: GirlieMac's stuff tagged with http (Wednesday, 14 December)

Adam Barth

• Re: lower casing host names (Saturday, 31 December)
• Re: lower casing host names (Saturday, 31 December)
• Re: #322: Origin (Thursday, 15 December)

Adrian Custer

• Is the ABNF for <request-target> in HTTPbis too general? (Friday, 14 October)

Adrien de Croy

• Re: lower casing host names (Friday, 30 December)
• Re: best status code for bad auth method (Friday, 9 December)
• Re: best status code for bad auth method (Friday, 9 December)
• Re: best status code for bad auth method (Friday, 9 December)
• best status code for bad auth method (Friday, 9 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• Re: #311: Denial of Service and Ranges (Thursday, 24 November)
• Re: #312: should there be a permanent variant of 307? (Saturday, 29 October)
• Proxy-Authorization with empty credentials (Wednesday, 5 October)

Alex Rousskov

• Re: Prefer Draft Feedback (Monday, 19 December)
• Re: #327: Expect syntax (Friday, 16 December)
• Re: #327: Expect syntax (Friday, 16 December)
• Re: #327: Expect syntax (Thursday, 15 December)
• Re: #327: Expect syntax (Wednesday, 14 December)
• Re: Prefer Draft Feedback (Monday, 12 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 8 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 8 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Wednesday, 7 December)
• Re: Partially fulfilled / draft-nottingham-http-new-status (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Partially fulfilled / draft-nottingham-http-new-status (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Saturday, 3 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 1 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)

Alexander Dutton

• Re: Additional HTTP Status Codes - "Request Too Onerous" (Thursday, 10 November)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Wednesday, 9 November)
• Additional HTTP Status Codes - "Request Too Onerous" (Wednesday, 9 November)

Amos Jeffries

• Re: OAuth Bearer authentication - for proxies? (Saturday, 31 December)
• Re: OAuth Bearer authentication - for proxies? (Sunday, 25 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: Getting to Last Call (Thursday, 15 December)
• Re: Getting to Last Call (Thursday, 15 December)
• Re: Negotiated private cache storage allocation (Wednesday, 14 December)
• Re: "Accept" on 415 responses? (Tuesday, 13 December)
• Re: "Accept" on 415 responses? (Tuesday, 13 December)
• Re: "Accept" on 415 responses? (Monday, 12 December)
• Re: best status code for bad auth method (Friday, 9 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: HTTP header field syntax [WAS: Re: Prefer Draft Feedback] (Wednesday, 7 December)
• HTTP header field syntax [WAS: Re: Prefer Draft Feedback] (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Tuesday, 6 December)
• Re: #158: Proxy-Connection and Keep-alive (Tuesday, 29 November)
• Re: #274: Warn-code registry (Tuesday, 29 November)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 28 November)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 28 November)
• Re: Possible issue: Accept-language priority based on language order (Sunday, 27 November)
• Re: Possible issue: Accept-language priority based on language order (Wednesday, 23 November)
• Re: ID draft-petersson-forwarded-for-02.txt (Friday, 18 November)

Andreas Petersson

• Re: ID draft-petersson-forwarded-for-02.txt (Sunday, 4 December)
• Re: ID draft-petersson-forwarded-for-02.txt (Tuesday, 22 November)
• ID draft-petersson-forwarded-for-02.txt (Thursday, 17 November)
• Re: I-D draft-petersson-forwarded-for-01.txt (Monday, 10 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Saturday, 8 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Friday, 7 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Wednesday, 5 October)
• I-D draft-petersson-forwarded-for-01.txt (Wednesday, 5 October)

Anne van Kesteren

• Re: lower casing host names (Saturday, 31 December)
• Re: Protocols/APIs and redirects (Thursday, 8 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Tuesday, 6 December)
• Protocols/APIs and redirects (Tuesday, 6 December)

bergi

• Re: HTTP request header field for acceptable authentication methods (Thursday, 3 November)

Bjoern Hoehrmann

• Re: Additional HTTP Status Codes - "Request Too Onerous" (Wednesday, 9 November)

Cameron Heavon-Jones

• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Thursday, 15 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: Restoring PUT and DELETE (Wednesday, 7 December)
• Re: Restoring PUT and DELETE (Friday, 2 December)

Dale Anderson

• Re: lower casing host names (Friday, 30 December)
• Re: fya: Flickr: GirlieMac's stuff tagged with http (Thursday, 15 December)
• Re: best status code for bad auth method (Saturday, 10 December)
• Re: HTTP header field syntax [WAS: Re: Prefer Draft Feedback] (Wednesday, 7 December)
• Re: #311: Denial of Service and Ranges (Thursday, 24 November)
• Re: Possible issue: Accept-language priority based on language order (Thursday, 24 November)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Saturday, 12 November)
• Re: Unicode in HTTP headers (was Re: json-string for HTTP header field parameter values) (Friday, 11 November)
• Re: IPV6 literal URL format mention might be useful (Friday, 7 October)
• IPV6 literal URL format mention might be useful (Friday, 7 October)

Dan Anderson

• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Thursday, 20 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Thursday, 20 October)
• Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Wednesday, 19 October)

Dan Winship

• Re: Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 (Tuesday, 20 December)

Daniel Stenberg

• Re: lower casing host names (Saturday, 31 December)
• lower casing host names (Friday, 30 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: best status code for bad auth method (Friday, 9 December)

Darrel Miller

• Re: I-D draft-petersson-forwarded-for-01.txt (Tuesday, 11 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Wednesday, 5 October)

David Morris

• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Friday, 16 December)
• Re: Feedback sought on timezone header for HTTP (Thursday, 8 December)
• Re: Feedback sought on timezone header for HTTP (Thursday, 8 December)
• RE: json-string for HTTP header field parameter values (Monday, 31 October)
• Re: Cache-Control directive case sensitivity (Monday, 17 October)

Dmitry Kurochkin

• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Saturday, 3 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• issue 11: URI includes query (Friday, 11 November)

Dominik Tomaszuk

• Re: HTTP request header field for acceptable authentication methods (Monday, 31 October)

Harald Alvestrand

• Re: Possible issue: Accept-language priority based on language order (Sunday, 27 November)
• Re: Possible issue: Accept-language priority based on language order (Sunday, 27 November)
• Re: Possible issue: Accept-language priority based on language order (Thursday, 24 November)
• Re: Possible issue: Accept-language priority based on language order (Wednesday, 23 November)
• Possible issue: Accept-language priority based on language order (Wednesday, 23 November)

Henry Story

• Re: [foaf-protocols] HTTP request header field for acceptable authentication methods (Saturday, 5 November)

Herbert van de Sompel

• New version of Memento Internet Draft (Tuesday, 20 December)
• Re: Protocols/APIs and redirects (Friday, 9 December)

Håkan

• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Wednesday, 26 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Wednesday, 26 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Wednesday, 26 October)
• draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Tuesday, 25 October)

internet-drafts@ietf.org

• I-D Action: draft-ietf-httpbis-p4-conditional-17.txt (Monday, 31 October)
• I-D Action: draft-ietf-httpbis-p3-payload-17.txt (Monday, 31 October)
• I-D Action: draft-ietf-httpbis-p2-semantics-17.txt (Monday, 31 October)
• I-D Action: draft-ietf-httpbis-p1-messaging-17.txt (Monday, 31 October)
• I-D Action: draft-ietf-httpbis-p7-auth-17.txt (Monday, 31 October)
• I-D Action: draft-ietf-httpbis-p6-cache-17.txt (Monday, 31 October)
• I-D Action: draft-ietf-httpbis-p5-range-17.txt (Monday, 31 October)

James Snell

• Re: Prefer Draft Feedback (Monday, 19 December)
• Re: Prefer Draft Feedback (Monday, 19 December)
• Re: Prefer Draft Feedback (Monday, 19 December)
• Re: Prefer Draft Feedback (Tuesday, 13 December)
• Re: Prefer Draft Feedback (Tuesday, 13 December)
• Re: Prefer Draft Feedback (Monday, 12 December)
• Re: Prefer Draft Feedback (Monday, 12 December)
• Re: I-D Action: draft-reschke-rfc5987bis-03.txt (Thursday, 8 December)
• Re: Prefer Draft Feedback (Thursday, 8 December)
• Re: Prefer Draft Feedback (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Wednesday, 7 December)
• RE: Prefer Draft Feedback (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Monday, 5 December)
• Re: Prefer Draft Feedback (Monday, 5 December)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Monday, 5 December)
• Re: Prefer Draft Feedback (Monday, 5 December)
• Re: Prefer Draft Feedback (Monday, 5 December)
• Re: Prefer Draft Feedback (Monday, 5 December)
• Prefer Draft Feedback (Friday, 2 December)
• Re: draft-snell-http-prefer (Tuesday, 25 October)
• Re: 202 Accepted, Location, and Retry-After (Tuesday, 25 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Wednesday, 19 October)
• Re: draft-snell-http-prefer (Tuesday, 18 October)
• Re: draft-snell-http-prefer (Monday, 17 October)
• Re: draft-snell-http-prefer (Monday, 17 October)

Jan Algermissen

• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Friday, 16 December)

Joe Presbrey

• Re: [foaf-protocols] HTTP request header field for acceptable authentication methods (Saturday, 5 November)

Jonathan Billington

• RE: Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 (Wednesday, 21 December)
• RE: Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 (Tuesday, 20 December)
• Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 (Tuesday, 20 December)

Julian Reschke

• Re: #295: Applying original fragment to "plain" redirected URI (also #43) (Friday, 30 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Friday, 30 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Friday, 30 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Tuesday, 27 December)
• Re: OAuth Bearer authentication - for proxies? (Sunday, 25 December)
• Re: Fwd: [Technical Errata Reported] RFC2616 (3056) (Wednesday, 21 December)
• Re: #185: Location header payload handling (Tuesday, 20 December)
• #312 (should there be a permanent variant of 307), was: I-D Action: draft-reschke-http-status-308-00.txt (Monday, 19 December)
• Fwd: I-D Action: draft-reschke-rfc5987bis-04.txt (Sunday, 18 December)
• Re: #327: Expect syntax (Sunday, 18 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• RFC5987bis parmsyntax, was: json-string for HTTP header field parameter values (Saturday, 17 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: #327: Expect syntax (Friday, 16 December)
• Re: #185: Location header payload handling (Friday, 16 December)
• Re: #327: Expect syntax (Friday, 16 December)
• Re: Last Call: <draft-nottingham-http-new-status-03.txt> (Additional HTTP Status Codes) to Proposed Standard (Friday, 16 December)
• Re: Getting to Last Call (Friday, 16 December)
• Re: #327: Expect syntax (Thursday, 15 December)
• Re: #327: Expect syntax (Thursday, 15 December)
• Re: fya: Flickr: GirlieMac's stuff tagged with http (Wednesday, 14 December)
• Re: #329: header field considerations: quoted-string vs use of double quotes (Wednesday, 14 December)
• Re: #327: Expect syntax (Wednesday, 14 December)
• #327: Expect syntax, was: Prefer Draft Feedback (Wednesday, 14 December)
• #329: header field considerations: quoted-string vs use of double quotes (Wednesday, 14 December)
• Re: #322: Origin (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: #322: Origin (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: Prefer Draft Feedback (Wednesday, 14 December)
• Re: Prefer Draft Feedback (Tuesday, 13 December)
• Re: Prefer Draft Feedback (Tuesday, 13 December)
• "Accept" on 415 responses? (Monday, 12 December)
• Re: Prefer Draft Feedback (Monday, 12 December)
• Re: I-D Action: draft-reschke-rfc5987bis-03.txt (Friday, 9 December)
• Re: Feedback sought on timezone header for HTTP (Thursday, 8 December)
• Re: Feedback sought on timezone header for HTTP (Thursday, 8 December)
• Fwd: I-D Action: draft-reschke-rfc5987bis-03.txt (Thursday, 8 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 8 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: HTTP header field syntax [WAS: Re: Prefer Draft Feedback] (Wednesday, 7 December)
• issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: HTTP header field syntax [WAS: Re: Prefer Draft Feedback] (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Feedback sought on timezone header for HTTP (Tuesday, 6 December)
• Re: Protocols/APIs and redirects (Tuesday, 6 December)
• Re: Protocols/APIs and redirects (Tuesday, 6 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Monday, 5 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Monday, 5 December)
• Re: Prefer Draft Feedback (Monday, 5 December)
• Re: Prefer Draft Feedback (Monday, 5 December)
• Re: status code for header fields to big (Monday, 5 December)
• Re: Prefer Draft Feedback (Sunday, 4 December)
• Re: Prefer Draft Feedback (Saturday, 3 December)
• Re: #255 and #299: Status code semantics (Saturday, 3 December)
• Re: status code for header fields to big (Saturday, 3 December)
• Re: status code for header fields to big (Friday, 2 December)
• Re: I-D Action: draft-nottingham-http-new-status-00.txt (Friday, 2 December)
• Re: status code for header fields to big (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: Restoring PUT and DELETE (Thursday, 1 December)
• Fwd: Re: Restoring PUT and DELETE (Thursday, 1 December)
• Re: #274: Warn-code registry (Tuesday, 29 November)
• Re: Possible issue: Accept-language priority based on language order (Sunday, 27 November)
• Re: #324: URI includes query (Saturday, 26 November)
• Re: Possible issue: Accept-language priority based on language order (Saturday, 26 November)
• Re: #314: realm parameter syntax (Friday, 25 November)
• Re: Possible issue: Accept-language priority based on language order (Friday, 25 November)
• Re: Possible issue: Accept-language priority based on language order (Thursday, 24 November)
• Re: Possible issue: Accept-language priority based on language order (Wednesday, 23 November)
• Re: Possible issue: Accept-language priority based on language order (Wednesday, 23 November)
• Re: #314: realm parameter syntax (Sunday, 20 November)
• #314: realm parameter syntax (Sunday, 20 November)
• Re: Target maturity level for HTTPbis (Monday, 14 November)
• Re: #312: should there be a permanent variant of 307? (Friday, 11 November)
• Re: #312: should there be a permanent variant of 307? (Friday, 11 November)
• Re: #324: URI includes query (Friday, 11 November)
• Re: issue 11: URI includes query (Friday, 11 November)
• Re: #312: should there be a permanent variant of 307? (Friday, 11 November)
• Re: #321: Repeating auth-params (Thursday, 10 November)
• #321: Repeating auth-params (Tuesday, 8 November)
• Re: #300: Define non-final responses (Saturday, 5 November)
• Re: #312: should there be a permanent variant of 307? (Friday, 4 November)
• Re: #300: Define non-final responses (Friday, 4 November)
• Re: #320: add advice on defining auth scheme parameters (Friday, 4 November)
• Re: #312: should there be a permanent variant of 307? (Friday, 4 November)
• Re: #312: should there be a permanent variant of 307? (Wednesday, 2 November)
• Re: #160: Redirects and non-GET methods (Wednesday, 2 November)
• Re: #306: does etag value really use quoted-string (Wednesday, 2 November)
• Re: json-string for HTTP header field parameter values (Wednesday, 2 November)
• Re: #320: add advice on defining auth scheme parameters (Tuesday, 1 November)
• Re: #320: add advice on defining auth scheme parameters (Monday, 31 October)
• httpbis -17 drafts (Monday, 31 October)
• Re: json-string for HTTP header field parameter values (Monday, 31 October)
• Re: #320: add advice on defining auth scheme parameters (Monday, 31 October)
• Re: #320: add advice on defining auth scheme parameters (Sunday, 30 October)
• Re: #320: add advice on defining auth scheme parameters (Saturday, 29 October)
• Re: #320: add advice on defining auth scheme parameters (Saturday, 29 October)
• Re: #306: does etag value really use quoted-string (Saturday, 29 October)
• Re: #320: add advice on defining auth scheme parameters (Friday, 28 October)
• #312: should there be a permanent variant of 307? (Thursday, 27 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Thursday, 27 October)
• #320: add advice on defining auth scheme parameters (Thursday, 27 October)
• Re: #231: Considerations for new headers (Thursday, 27 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Wednesday, 26 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Wednesday, 26 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Wednesday, 26 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Wednesday, 26 October)
• Re: #318, was: Closing the connection (Wednesday, 26 October)
• Re: #318, was: Closing the connection (Tuesday, 25 October)
• #318, was: Closing the connection (Tuesday, 25 October)
• Re: #297: p1 7.2.4: retrying requests (Tuesday, 25 October)
• Re: #306: does etag value really use quoted-string (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: #300: Define non-final responses (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: #297: p1 7.2.4: retrying requests (Monday, 24 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: #297: p1 7.2.4: retrying requests (Monday, 24 October)
• Closing the connection (Monday, 24 October)
• Re: #186: Document HTTP's error-handling philosophy (Sunday, 23 October)
• Re: Fwd: I-D Action: draft-nottingham-http-new-status-02.txt (Saturday, 22 October)
• Re: Cache-Control directive case sensitivity (Monday, 17 October)
• Re: #231: Considerations for new headers (Sunday, 16 October)
• Re: #231: Considerations for new headers (Friday, 14 October)
• Re: #231: Considerations for new headers (Thursday, 13 October)
• Re: #231: Considerations for new headers (Tuesday, 11 October)
• Re: #231: Considerations for new headers (Monday, 10 October)
• Re: IPV6 literal URL format mention might be useful (Friday, 7 October)
• Re: [#95] Multiple Content-Lengths (Sunday, 2 October)

Jói Sigurðsson

• Re: Feedback on draft-sigurdsson-anti-ddos-http-throttling (Wednesday, 12 October)
• Re: Feedback on draft-sigurdsson-anti-ddos-http-throttling (Monday, 10 October)

Karl Dubost

• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 8 December)
• Re: Feedback sought on timezone header for HTTP (Thursday, 8 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 8 December)

Larry Masinter

• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Tuesday, 27 December)
• RE: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Friday, 16 December)
• RE: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 15 December)
• RE: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 8 December)

Manger, James H

• RE: json-string for HTTP header field parameter values (Wednesday, 2 November)
• RE: json-string for HTTP header field parameter values (Monday, 31 October)
• RE: json-string for HTTP header field parameter values (Monday, 31 October)
• json-string for HTTP header field parameter values (Sunday, 30 October)
• RE: #231: Considerations for new headers (Friday, 14 October)

Mark Baker

• Re: #312: should there be a permanent variant of 307? (Saturday, 29 October)

Mark Nottingham

• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Saturday, 31 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Friday, 30 December)
• Re: Getting to Last Call (Friday, 30 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Friday, 30 December)
• Re: Getting to Last Call (Saturday, 24 December)
• OAuth Bearer authentication - for proxies? (Saturday, 24 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Saturday, 24 December)
• Re: #322: Origin (Saturday, 24 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 15 December)
• Getting to Last Call (Thursday, 15 December)
• Re: #185: Location header payload handling (Thursday, 15 December)
• Re: fya: Flickr: GirlieMac's stuff tagged with http (Wednesday, 14 December)
• Re: #329: header field considerations: quoted-string vs use of double quotes (Wednesday, 14 December)
• Re: Negotiated private cache storage allocation (Wednesday, 14 December)
• Re: #322: Origin (Wednesday, 14 December)
• Re: Negotiated private cache storage allocation (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• #185: Location header payload handling (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• #322: Origin (Wednesday, 14 December)
• Re: #158: Proxy-Connection and Keep-alive (Wednesday, 14 December)
• Re: best status code for bad auth method (Saturday, 10 December)
• Re: Protocols/APIs and redirects (Friday, 9 December)
• Re: #158: Proxy-Connection and Keep-alive (Friday, 9 December)
• Re: best status code for bad auth method (Friday, 9 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 8 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 8 December)
• Re: Protocols/APIs and redirects (Thursday, 8 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 8 December)
• Re: [apps-discuss] Partially fulfilled / draft-nottingham-http-new-status (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Wednesday, 7 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Wednesday, 7 December)
• Re: #311: Denial of Service and Ranges (Wednesday, 7 December)
• Re: Partially fulfilled / draft-nottingham-http-new-status (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Monday, 5 December)
• Re: Discussion Place for CGI/1.1 (Monday, 5 December)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 5 December)
• Re: [apps-discuss] Discussion Place for CGI/1.1 (Monday, 5 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Monday, 5 December)
• Re: status code for header fields to big (Monday, 5 December)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 5 December)
• #293: Interaction of request and response Cache-Control (Saturday, 3 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Saturday, 3 December)
• Re: #158: Proxy-Connection and Keep-alive (Saturday, 3 December)
• Re: #274: Warn-code registry (Saturday, 3 December)
• #255 and #299: Status code semantics (Friday, 2 December)
• Re: Restoring PUT and DELETE (Thursday, 1 December)
• Re: Restoring PUT and DELETE (Thursday, 1 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 1 December)
• #274: Warn-code registry (Tuesday, 29 November)
• #212: Refining Age for proxy chains (Tuesday, 29 November)
• #158: Proxy-Connection and Keep-alive (Monday, 28 November)
• Re: Possible issue: Accept-language priority based on language order (Sunday, 27 November)
• #311: Denial of Service and Ranges (Thursday, 24 November)
• Re: [apps-discuss] I-D Action: draft-nottingham-http-new-status-02.txt (Monday, 14 November)
• Target maturity level for HTTPbis (Sunday, 13 November)
• #324: URI includes query (Friday, 11 November)
• Re: #312: should there be a permanent variant of 307? (Friday, 11 November)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Wednesday, 9 November)
• Issues addressed in the -17 drafts (Saturday, 5 November)
• Re: SHOULD-level requirements in p6-caching (Saturday, 5 November)
• Re: SHOULD-level requirements in p6-caching (Saturday, 5 November)
• Re: [foaf-protocols] HTTP request header field for acceptable authentication methods (Saturday, 5 November)
• Re: #300: Define non-final responses (Saturday, 5 November)
• Re: HTTP request header field for acceptable authentication methods (Friday, 4 November)
• Re: #312: should there be a permanent variant of 307? (Thursday, 3 November)
• Re: #306: does etag value really use quoted-string (Wednesday, 2 November)
• Re: HTTP request header field for acceptable authentication methods (Wednesday, 2 November)
• Re: Unicode in HTTP headers (was Re: json-string for HTTP header field parameter values) (Monday, 31 October)
• Re: json-string for HTTP header field parameter values (Monday, 31 October)
• Re: #320: add advice on defining auth scheme parameters (Monday, 31 October)
• Re: json-string for HTTP header field parameter values (Monday, 31 October)
• Re: #320: add advice on defining auth scheme parameters (Saturday, 29 October)
• Re: #312: should there be a permanent variant of 307? (Friday, 28 October)
• OWS before chunk (Thursday, 27 October)
• Re: #318, was: Closing the connection (Wednesday, 26 October)
• Re: #300: Define non-final responses (Tuesday, 25 October)
• Re: #318, was: Closing the connection (Tuesday, 25 October)
• Re: draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example? (Tuesday, 25 October)
• Re: 202 Accepted, Location, and Retry-After (Tuesday, 25 October)
• Re: Closing the connection (Tuesday, 25 October)
• Re: #297: p1 7.2.4: retrying requests (Monday, 24 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Sunday, 23 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Sunday, 23 October)
• Re: I-D Action: draft-nottingham-http-new-status-02.txt (Sunday, 23 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Saturday, 22 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Thursday, 20 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Thursday, 20 October)
• Re: [apps-discuss] Fwd: I-D Action: draft-nottingham-http-new-status-02.txt (Wednesday, 19 October)
• Fwd: I-D Action: draft-nottingham-http-new-status-02.txt (Tuesday, 18 October)
• [#317] Cache-Control directive case sensitivity (Monday, 17 October)
• Re: draft-snell-http-prefer (Monday, 17 October)
• Cache-Control directive case sensitivity (Monday, 17 October)
• Re: #231: Considerations for new headers (Thursday, 13 October)
• Re: Feedback on draft-sigurdsson-anti-ddos-http-throttling (Wednesday, 12 October)
• Re: #231: Considerations for new headers (Monday, 10 October)
• Feedback on draft-sigurdsson-anti-ddos-http-throttling (Monday, 10 October)
• draft-snell-http-prefer (Friday, 7 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Thursday, 6 October)

Markus Lanthaler

• RE: Partially fulfilled / draft-nottingham-http-new-status (Wednesday, 7 December)
• RE: Partially fulfilled / draft-nottingham-http-new-status (Wednesday, 7 December)
• RE: Partially fulfilled / draft-nottingham-http-new-status (Tuesday, 6 December)
• Partially fulfilled / draft-nottingham-http-new-status (Tuesday, 6 December)

Martin J. Dürst

• Re: Possible issue: Accept-language priority based on language order (Thursday, 24 November)

Martin Thomson

• Re: Prefer Draft Feedback (Saturday, 10 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)

Matthew Fenelon

• RE: Feedback sought on timezone header for HTTP (Tuesday, 13 December)
• Feedback sought on timezone header for HTTP (Tuesday, 6 December)

mike amundsen

• Re: "Accept" on 415 responses? (Tuesday, 13 December)
• Re: "Accept" on 415 responses? (Monday, 12 December)
• Re: Restoring PUT and DELETE (Wednesday, 7 December)
• Re: Restoring PUT and DELETE (Friday, 2 December)
• Re: Restoring PUT and DELETE (Thursday, 1 December)

Mike Kelly

• Re: Negotiated private cache storage allocation (Thursday, 15 December)
• Re: Negotiated private cache storage allocation (Wednesday, 14 December)
• Re: Negotiated private cache storage allocation (Wednesday, 14 December)
• Negotiated private cache storage allocation (Wednesday, 14 December)

Moore, Jonathan (CIM)

• Re: Prefer Draft Feedback (Wednesday, 7 December)
• RE: Prefer Draft Feedback (Wednesday, 7 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Prefer Draft Feedback (Tuesday, 6 December)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Monday, 14 November)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Thursday, 10 November)

Mykyta Yevstifeyev

• Re: [apps-discuss] Fwd: I-D Action: draft-nottingham-http-new-status-02.txt (Wednesday, 19 October)

Patrick McManus

• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 1 December)

Peter Saint-Andre

• Re: Fwd: [Technical Errata Reported] RFC2616 (3056) (Wednesday, 21 December)
• Fwd: [Technical Errata Reported] RFC2616 (3056) (Tuesday, 20 December)
• Fwd: Last Call: <draft-nottingham-http-new-status-03.txt> (Additional HTTP Status Codes) to Proposed Standard (Friday, 16 December)
• Re: Getting to Last Call (Thursday, 15 December)
• Re: Partially fulfilled / draft-nottingham-http-new-status (Wednesday, 7 December)
• Re: status code for header fields to big (Friday, 2 December)
• Re: I-D Action: draft-nottingham-http-new-status-00.txt (Friday, 2 December)
• Re: status code for header fields to big (Friday, 2 December)
• Re: status code for header fields to big (Friday, 2 December)
• Re: I-D Action: draft-nottingham-http-new-status-00.txt (Friday, 2 December)
• Re: Target maturity level for HTTPbis (Monday, 14 November)
• RFC 2617 erratum (Sunday, 13 November)
• The "Bearer" Authentication Scheme (draft-ietf-oauth-v2-bearer) (Wednesday, 9 November)
• Re: I-D draft-petersson-forwarded-for-01.txt (Monday, 17 October)

Peter Williams

• RE: [foaf-protocols] HTTP request header field for acceptable authentication methods (Saturday, 5 November)
• Re: [foaf-protocols] HTTP request header field for acceptable authentication methods (Saturday, 5 November)

Poul-Henning Kamp

• Re: Discussion Place for CGI/1.1 (Monday, 5 December)
• Re: Discussion Place for CGI/1.1 (Monday, 5 December)
• Re: I-D draft-petersson-forwarded-for-01.txt (Thursday, 6 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Thursday, 6 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Wednesday, 5 October)
• Re: I-D draft-petersson-forwarded-for-01.txt (Wednesday, 5 October)

Randall Gellens

• Re: [apps-discuss] I-D Action: draft-nottingham-http-new-status-02.txt (Monday, 14 November)

Riccardo Bernardini

• Re: Last Call: <draft-nottingham-http-new-status-03.txt> (Additional HTTP Status Codes) to Proposed Standard (Friday, 16 December)

Robert Collins

• Re: #311: Denial of Service and Ranges (Thursday, 24 November)

Roy T. Fielding

• Re: lower casing host names (Saturday, 31 December)
• Re: lower casing host names (Friday, 30 December)
• Re: Getting to Last Call (Friday, 30 December)
• Re: #322: Origin (Wednesday, 14 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 8 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 8 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: Partially fulfilled / draft-nottingham-http-new-status (Wednesday, 7 December)
• Re: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: #318, was: Closing the connection (Wednesday, 26 October)
• Re: 202 Accepted, Location, and Retry-After (Monday, 24 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Sunday, 23 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Saturday, 22 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Friday, 21 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Wednesday, 19 October)
• Re: Is the ABNF for <request-target> in HTTPbis too general? (Tuesday, 18 October)

Sam Johnston

• Re: Partially fulfilled / draft-nottingham-http-new-status (Tuesday, 6 December)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Wednesday, 9 November)
• Unicode in HTTP headers (was Re: json-string for HTTP header field parameter values) (Monday, 31 October)
• Re: Cache-Control directive case sensitivity (Monday, 17 October)

Thomas Fossati

• Re: "Accept" on 415 responses? (Tuesday, 13 December)

Thomson, Martin

• RE: json-string for HTTP header field parameter values (Monday, 31 October)
• RE: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Thursday, 20 October)
• RE: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Wednesday, 19 October)
• RE: draft-snell-http-prefer (Monday, 17 October)
• RE: I-D draft-petersson-forwarded-for-01.txt (Monday, 10 October)
• RE: I-D draft-petersson-forwarded-for-01.txt (Friday, 7 October)
• RE: I-D draft-petersson-forwarded-for-01.txt (Friday, 7 October)
• RE: I-D draft-petersson-forwarded-for-01.txt (Thursday, 6 October)

TianLinyi

• Re: [apps-discuss] I-D Action: draft-nottingham-http-new-status-02.txt (Monday, 14 November)

William A. Rowe Jr.

• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 8 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Thursday, 8 December)
• Re: #311: Denial of Service and Ranges (Thursday, 24 November)
• Re: Additional HTTP Status Codes - "Request Too Onerous" (Monday, 14 November)

Willy Tarreau

• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Friday, 30 December)
• Re: Getting to Last Call (Friday, 30 December)
• Re: Getting to Last Call (Sunday, 25 December)
• Re: Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 (Wednesday, 21 December)
• Re: Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17 (Tuesday, 20 December)
• Re: #327: Expect syntax (Sunday, 18 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: #327: Expect syntax (Saturday, 17 December)
• Re: Getting to Last Call (Thursday, 15 December)
• Re: Getting to Last Call (Thursday, 15 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 14 December)
• Re: "Accept" on 415 responses? (Tuesday, 13 December)
• Re: #158: Proxy-Connection and Keep-alive (Friday, 9 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 8 December)
• Re: issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects (Wednesday, 7 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Wednesday, 7 December)
• Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs (Monday, 5 December)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 5 December)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 5 December)
• Re: #158: Proxy-Connection and Keep-alive (Saturday, 3 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Saturday, 3 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Friday, 2 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Thursday, 1 December)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• Re: #158: Proxy-Connection and Keep-alive (Tuesday, 29 November)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• Re: clarify some MUST requirements in HTTPbis part 1 section 3.3 (Tuesday, 29 November)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 28 November)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 28 November)
• Re: #158: Proxy-Connection and Keep-alive (Monday, 28 November)
• Re: SHOULD-level requirements in p6-caching (Saturday, 5 November)
• Re: SHOULD-level requirements in p6-caching (Saturday, 5 November)
• Re: #320: add advice on defining auth scheme parameters (Saturday, 29 October)
• Re: #320: add advice on defining auth scheme parameters (Saturday, 29 October)
• Re: Additional HTTP Status Codes - draft-nottingham-http-new-status-02 (Thursday, 20 October)
• Re: Proxy-Authorization with empty credentials (Saturday, 8 October)

Yutaka OIWA

• Re: best status code for bad auth method (Friday, 9 December)
• Discussion Place for CGI/1.1 (Monday, 5 December)
• Re: #314: realm parameter syntax (Sunday, 20 November)
• Re: [apps-discuss] I-D Action: draft-nottingham-http-new-status-02.txt (Monday, 14 November)
• Re: HTTP request header field for acceptable authentication methods (Thursday, 3 November)
• Re: #320: add advice on defining auth scheme parameters (Thursday, 3 November)
• Re: #320: add advice on defining auth scheme parameters (Monday, 31 October)
• Re: #320: add advice on defining auth scheme parameters (Monday, 31 October)
• Re: #320: add advice on defining auth scheme parameters (Saturday, 29 October)
• Re: OT re HTTP auth disassocation of credentials (Tuesday, 4 October)

Yves Lafon

• Re: #311: Denial of Service and Ranges (Thursday, 8 December)
• Re: #312: should there be a permanent variant of 307? (Friday, 4 November)
• Re: #312: should there be a permanent variant of 307? (Friday, 28 October)
• Content-Range on responses other than 206 (Thursday, 27 October)
• [#319] Case sensitivity in p5 (Thursday, 27 October)

Zhi-Qiang Lei

• The priority of Content-Encoding and Content-Range (Sunday, 30 October)

陈智昌

• Re: Getting to Last Call (Friday, 16 December)
• Re: [#95] Multiple Content-Lengths (Sunday, 2 October)

Last message date: Saturday, 31 December 2011 19:38:50 UTC