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

=JeffH

IETF BoF @IETF-78 Maastricht: HASMAT - HTTP Application Security Minus Authentication and Transport (Wednesday, 9 June)

Adam Barth

Re: Handling multiple headers when only one is allowed (Friday, 18 June)

Adrien de Croy

semantic equivalence of delimiters in URIs (Thursday, 17 June)
Re: "actual content length", was: Handling multiple headers when only one is allowed (Friday, 11 June)
Re: Fwd: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 9 June)
Re: Fwd: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 9 June)
Re: Fwd: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 9 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Wednesday, 9 June)
Re: Handling multiple headers when only one is allowed (Wednesday, 9 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: #168: understanding CC directives (Monday, 7 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: update: http progress notification (Friday, 28 May)
Re: update: http progress notification (Thursday, 27 May)
Re: update: http progress notification (Thursday, 27 May)
Re: update: http progress notification (Thursday, 27 May)
Re: http progress notification (Wednesday, 26 May)
Re: http progress notification (Tuesday, 25 May)
Re: http progress notification (Tuesday, 25 May)
Re: http progress notification (Tuesday, 25 May)
Re: http progress notification (Tuesday, 25 May)
http progress notification (Tuesday, 25 May)
update: http progress notification (Monday, 24 May)
304 updating ETag (Monday, 17 May)
Re: Expect: 100-continue and proxies (Sunday, 16 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
Re: In support of sending fragment IDs to the server (issue #43) (Monday, 3 May)
Re: Age response header and HTTP/1.0 requests (Tuesday, 6 April)
Age response header and HTTP/1.0 requests (Tuesday, 6 April)
Re: 100 Continue and Expects (Thursday, 1 April)

Anne van Kesteren

Re: Handling multiple headers when only one is allowed (Wednesday, 9 June)

Bert Bos

In support of sending fragment IDs to the server (issue #43) (Monday, 3 May)

Bil Corry

Handling multiple headers when only one is allowed (Wednesday, 9 June)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Saturday, 15 May)

Bjoern Hoehrmann

Re: clarity needed for browser behaviors when receiving 206 status codes (Friday, 25 June)

Brian Smith

RE: pack200-gzip Content Coding (Saturday, 10 April)
RE: pack200-gzip Content Coding (Friday, 9 April)

Dan Winship

Re: "actual content length", was: Handling multiple headers when only one is allowed (Friday, 11 June)
Re: Issue 163, was: Meaning of invalid but well-formed dates (Monday, 24 May)

Daniel Stenberg

Re: proposal for issue #178 (Monday, 7 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: update: http progress notification (Thursday, 27 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Wednesday, 19 May)
Re: Explicit instructions on use of fragment in request URI (Thursday, 22 April)

David Morris

Re: Questions (errata?) about caching authenticated responses [#174] (Tuesday, 8 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: http progress notification (Tuesday, 25 May)
Re: Query string cacheability (Friday, 21 May)

David Nuescheler

Re: pack200-gzip Content Coding (Friday, 9 April)

Elias Sinderson

Re: http progress notification (Tuesday, 25 May)

Eran Hammer-Lahav

RE: I-D Submission: draft-lee-httpext-metadata-00.txt (Saturday, 26 June)
Duplicating request component in an HTTP authentication scheme (Thursday, 27 May)
RE: Explicit instructions on use of fragment in request URI (Thursday, 22 April)
RE: Explicit instructions on use of fragment in request URI (Thursday, 22 April)
Explicit instructions on use of fragment in request URI (Thursday, 22 April)

Eric Lawrence

RE: Query string cacheability (Friday, 21 May)
RE: Query string cacheability (Wednesday, 19 May)

Greg Wilkins

Re: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 30 June)

Hausenblas, Michael

Re: I-D Submission: draft-lee-httpext-metadata-00.txt (Saturday, 26 June)

Henrik Nordstrom

Henrik Nordström

Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Monday, 21 June)
Re: semantic equivalence of delimiters in URIs (Monday, 21 June)
Re: semantic equivalence of delimiters in URIs (Saturday, 19 June)
Re: Managing multiple authorities, resources and representations (Sunday, 13 June)
Re: Managing multiple authorities, resources and representations (Sunday, 13 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Wednesday, 9 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Tuesday, 8 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Tuesday, 8 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: Duplicating request component in an HTTP authentication scheme (Sunday, 30 May)
Re: update: http progress notification (Thursday, 27 May)
Re: short-time client side caching and clock skew (Thursday, 27 May)
Re: update: http progress notification (Thursday, 27 May)
Re: update: http progress notification (Thursday, 27 May)
Re: update: http progress notification (Thursday, 27 May)
Re: update: http progress notification (Wednesday, 26 May)
Re: http progress notification (Wednesday, 26 May)
Re: http progress notification (Tuesday, 25 May)
Re: http progress notification (Tuesday, 25 May)
Re: http progress notification (Tuesday, 25 May)
Re: http progress notification (Tuesday, 25 May)
Re: Issue 163, was: Meaning of invalid but well-formed dates (Monday, 24 May)
Re: Explicit instructions on use of fragment in request URI (Monday, 24 May)
Re: Issue 163, was: Meaning of invalid but well-formed dates (Monday, 24 May)
Re: Query string cacheability (Thursday, 20 May)
Re: Query string cacheability (Thursday, 20 May)
Re: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
Re: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
[new issue] p1 messaging 4.2. fails to account for requested scheme which impacts http compared to https (Wednesday, 19 May)
Re: Same resource exposed over HTTP and HTTPS (Wednesday, 19 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Wednesday, 19 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Wednesday, 19 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: 304 updating ETag (Tuesday, 18 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: proposal for issue #178 (Monday, 17 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Monday, 17 May)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Saturday, 15 May)
Re: Expect: 100-continue and proxies (Saturday, 15 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Saturday, 15 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
Re: Clarification on use of Content-Location header (Friday, 14 May)
Re: FYI Cache-control deployment (Friday, 14 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 14 May)
RE: Clarification on use of Content-Location header (Friday, 14 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
RE: Multiple challenges in a single WWW-Authenticate header field (Friday, 14 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
Re: Cache behavior for authenticated contents (Friday, 14 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
Re: one time passwords from private keys (Friday, 14 May)
Re: What are "appropriate Cache-Control or Expires header fields" (Friday, 14 May)
RE: What are "appropriate Cache-Control or Expires header fields" (Friday, 14 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 14 May)
Re: 300 Multiple Choices and safe methods (Sunday, 9 May)
Re: proposal for issue #178 (Sunday, 9 May)
Re: proposal for issue #175 range flooding (Sunday, 9 May)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Sunday, 9 May)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Sunday, 9 May)
Re: 3 short questions, Entity Tag & Content Location (Sunday, 9 May)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 3 May)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 3 May)
Re: Transfer-Encoding in a HEAD response (Monday, 3 May)
Re: Issue 39: proposed example for varying the etag based on conneg (Monday, 3 May)
Re: Issue 39: proposed example for varying the etag based on conneg (Monday, 3 May)
Re: 100 Continue and Expects (Monday, 3 May)

Henry S. Thompson

Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Thursday, 17 June)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Wednesday, 9 June)

Honza Bambas

Missing specification in RFC 2617, cannot use a user name nor a password in encoding different from ISO-8859-1 (Monday, 3 May)

Houghton,Andrew

RE: Clarification on use of Content-Location header (Friday, 14 May)
Clarification on use of Content-Location header (Thursday, 13 May)

Jamie Lokier

Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Wednesday, 19 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Wednesday, 19 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Wednesday, 19 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 14 May)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 19 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 19 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 19 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: 100 Continue and Expects (Friday, 2 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Friday, 2 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Thursday, 1 April)
Re: 100 Continue and Expects (Thursday, 1 April)

Jan Algermissen

Re: Revisiting Retry-After w/ 202 (Thursday, 3 June)

Jeffrey Mogul

Re: Questions (errata?) about caching authenticated responses [#174] (Wednesday, 2 June)

Joe Orton

Re: Expect: 100-continue and proxies (Sunday, 16 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)

Jorrit Jongma

RE: short-time client side caching and clock skew (Tuesday, 1 June)
RE: short-time client side caching and clock skew (Monday, 31 May)
short-time client side caching and clock skew (Thursday, 27 May)

Julian Reschke

Re: NEW: value space of status codes [#213] (Tuesday, 29 June)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Tuesday, 29 June)
preparing new drafts for IETF 78 (Saturday, 26 June)
Re: clarity needed for browser behaviors when receiving 206 status codes (Friday, 25 June)
Re: clarity needed for browser behaviors when receiving 206 status codes (Friday, 25 June)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Tuesday, 15 June)
Re: "actual content length", was: Handling multiple headers when only one is allowed (Friday, 11 June)
Re: Handling multiple headers when only one is allowed (Wednesday, 9 June)
"actual content length", was: Handling multiple headers when only one is allowed (Wednesday, 9 June)
Re: [#211] Query string cacheability (Tuesday, 8 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: #168: understanding CC directives (Monday, 7 June)
Re: #168: understanding CC directives (Monday, 7 June)
#122 (MIME-Version not listed in P1, general header fields) (Wednesday, 2 June)
Re: #168: understanding CC directives (Wednesday, 2 June)
Re: [#211] Query string cacheability (Wednesday, 2 June)
Re: Broken link (Saturday, 29 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Wednesday, 26 May)
Re: Explicit instructions on use of fragment in request URI (Wednesday, 26 May)
Re: http progress notification (Wednesday, 26 May)
Re: Explicit instructions on use of fragment in request URI (Tuesday, 25 May)
Re: http progress notification (Tuesday, 25 May)
Re: Issue 163, was: Meaning of invalid but well-formed dates (Sunday, 23 May)
Issue 209, was: [new issue] p1 messaging 4.2. fails to account for requested scheme which impacts http compared to https (Thursday, 20 May)
Re: Query string cacheability (Thursday, 20 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Wednesday, 19 May)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Wednesday, 19 May)
Re: Query string cacheability (Wednesday, 19 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Wednesday, 19 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 18 May)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Sunday, 16 May)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Sunday, 16 May)
Fwd: [http-state] WG Last Call for draft-ietf-httpstate-cookie-08 ? (Monday, 10 May)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Sunday, 9 May)
Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Friday, 7 May)
ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Thursday, 6 May)
Revitalizing Caching ✩ Mozilla Hacks – the Web developer blog (Tuesday, 4 May)
Re: [http-state] Missing specification in RFC 2617, cannot use a user name nor a password in encoding different from ISO-8859-1 (Tuesday, 4 May)
Re: Protocol Action: 'Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters' to Proposed Standard (Friday, 30 April)
Labs/Weave/Identity/Account Manager/Spec/Latest - MozillaWiki (Friday, 30 April)
Re: I-D Action:draft-reschke-rfc2231-in-http-12.txt (Friday, 30 April)
Re: is rfc2616 the right document to study (Tuesday, 27 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 27 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Monday, 26 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Monday, 26 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Thursday, 22 April)
Re: Explicit instructions on use of fragment in request URI (Thursday, 22 April)
Re: Explicit instructions on use of fragment in request URI (Thursday, 22 April)
Re: Issue 200 ("word" in ABNF), was: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1 (Friday, 16 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Thursday, 15 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Wednesday, 14 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Wednesday, 14 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 13 April)
Issue 200 ("word" in ABNF), was: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1 (Monday, 12 April)
Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) (Saturday, 10 April)
Re: pack200-gzip Content Coding (Saturday, 10 April)
Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) (Friday, 9 April)
Re: pack200-gzip Content Coding (Friday, 9 April)
Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) (Friday, 9 April)
How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) (Thursday, 8 April)
pack200-gzip Content Coding (Thursday, 8 April)
Re: Issue 165, was: Issue 163, was: Meaning of invalid but well-formed dates (Wednesday, 7 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Ticket 183: "requested resource" in content-encoding definition (Tuesday, 6 April)
Issue 101, was: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 165, was: Issue 163, was: Meaning of invalid but well-formed dates (Friday, 2 April)
Re: #73: httpbis and deflate compression... (Thursday, 1 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Thursday, 1 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Thursday, 1 April)

Mark Nottingham

NEW: value space of status codes [#213] (Tuesday, 29 June)
Re: I-D Action:draft-loreto-http-timeout-00.txt (Tuesday, 29 June)
Fwd: HTTPBIS - Requested session has been scheduled for IETF 78 (Thursday, 24 June)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Saturday, 19 June)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Tuesday, 15 June)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Wednesday, 9 June)
Fwd: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 9 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Wednesday, 9 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Tuesday, 8 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Tuesday, 8 June)
Re: [#211] Query string cacheability (Tuesday, 8 June)
Fwd: I-D Action:draft-ietf-core-coap-00.txt (Tuesday, 8 June)
Re: #168: understanding CC directives (Thursday, 3 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Thursday, 3 June)
Re: short-time client side caching and clock skew [#212] (Wednesday, 2 June)
#168: understanding CC directives (Wednesday, 2 June)
Re: [#211] Query string cacheability (Wednesday, 2 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Wednesday, 2 June)
Re: short-time client side caching and clock skew (Tuesday, 1 June)
Re: What are "appropriate Cache-Control or Expires header fields" (Monday, 24 May)
Re: Explicit instructions on use of fragment in request URI (Sunday, 23 May)
Re: Issue 163, was: Meaning of invalid but well-formed dates (Sunday, 23 May)
[#211] Query string cacheability (Friday, 21 May)
Re: Query string cacheability (Friday, 21 May)
Re: Query string cacheability (Thursday, 20 May)
Query string cacheability (Wednesday, 19 May)
Re: TAG requests addition to section 3.2.1 of Part 3 [#155] (Wednesday, 19 May)
Fwd: RFC 5861 on HTTP Cache-Control Extensions for Stale Content (Thursday, 6 May)
Re: Issue 196, was: #110: how to determine what entity a response carries (Monday, 26 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Friday, 23 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 19 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 19 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Friday, 16 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Friday, 16 April)
Re: Issue 196, was: #110: how to determine what entity a response carries (Thursday, 15 April)
Re: Transfer-Encoding in a HEAD response (Tuesday, 13 April)
Re: Transfer-Encoding in a HEAD response (Sunday, 11 April)
Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) (Friday, 9 April)
Re: pack200-gzip Content Coding (Friday, 9 April)
Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189) (Friday, 9 April)
Re: Age response header and HTTP/1.0 requests (Tuesday, 6 April)
Fwd: I-D Action:draft-nottingham-http-link-header-09.txt (Saturday, 3 April)
Re: #73: httpbis and deflate compression... (Thursday, 1 April)

Mark Pauley

Re: 100 Continue and Expects (Friday, 2 April)
Re: 100 Continue and Expects (Thursday, 1 April)

Marques Johansson

Re: clarity needed for browser behaviors when receiving 206 status codes (Saturday, 26 June)
Re: clarity needed for browser behaviors when receiving 206 status codes (Friday, 25 June)
Re: clarity needed for browser behaviors when receiving 206 status codes (Friday, 25 June)
clarity needed for browser behaviors when receiving 206 status codes (Friday, 25 June)

Merin Tresa Willy

Re: 'Age' for web pages (Saturday, 12 June)
'Age' for web pages (Friday, 11 June)

mike amundsen

Re: Revisiting Retry-After w/ 202 (Thursday, 3 June)
Revisiting Retry-After w/ 202 (Thursday, 3 June)

Nathan

Re: Managing multiple authorities, resources and representations (Sunday, 13 June)
Re: Managing multiple authorities, resources and representations (Sunday, 13 June)
Re: 'Age' for web pages (Saturday, 12 June)
Re: 'Age' for web pages (Friday, 11 June)
Managing multiple authorities, resources and representations (Thursday, 10 June)
Re: Handling multiple headers when only one is allowed (Wednesday, 9 June)
Re: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
Re: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
Re: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
Re: Same resource exposed over HTTP and HTTPS (Wednesday, 19 May)
Same resource exposed over HTTP and HTTPS (Wednesday, 19 May)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Friday, 2 April)

Peter Saint-Andre

HTTP Application Security (HAS) BoF (Wednesday, 2 June)

Roy T. Fielding

Re: clarity needed for browser behaviors when receiving 206 status codes (Friday, 25 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Tuesday, 8 June)
Re: Questions (errata?) about caching authenticated responses [#174] (Tuesday, 8 June)
Re: proposal for issue #178 (Monday, 7 June)
Re: update: http progress notification (Friday, 28 May)
Re: Duplicating request component in an HTTP authentication scheme (Thursday, 27 May)
Re: update: http progress notification (Thursday, 27 May)
Re: update: http progress notification (Wednesday, 26 May)
Re: Query string cacheability (Thursday, 20 May)
Re: Query string cacheability (Wednesday, 19 May)
Re: Clarification on use of Content-Location header (Friday, 14 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
Re: Clarification on use of Content-Location header (Friday, 14 May)
Re: Expect: 100-continue and proxies (Friday, 14 May)
Re: Transfer-Encoding in a HEAD response (Wednesday, 14 April)

The Infrastructure Group via RT

[CSAIL #48734] AutoReply: Message received (Sunday, 20 June)
[CSAIL #48586] AutoReply: Re: Message received (Saturday, 19 June)

Thomas Broyer

Re: 'Age' for web pages (Saturday, 12 June)

Thomas Hühn

Broken link (Saturday, 29 May)

Thomson, Martin

RE: Fwd: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 9 June)
RE: Fwd: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 9 June)
RE: Fwd: I-D Action:draft-loreto-http-timeout-00.txt (Wednesday, 9 June)
RE: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
RE: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
RE: Issue 196, was: #110: how to determine what entity a response carries (Tuesday, 27 April)
RE: Issue 196, was: #110: how to determine what entity a response carries (Friday, 23 April)

transkawa

is rfc2616 the right document to study (Tuesday, 27 April)

Wenbo Zhu

Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 28 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Monday, 17 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Saturday, 15 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 14 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 14 May)
Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 14 May)
Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages") (Friday, 14 May)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Tuesday, 20 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Monday, 19 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Friday, 16 April)
Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages (Friday, 16 April)
clarification of 7.2.2. Monitoring Connections for Error Status Messages (Thursday, 15 April)
Re: Transfer-Encoding in a HEAD response (Thursday, 15 April)
Re: Transfer-Encoding in a HEAD response (Tuesday, 13 April)
Re: Transfer-Encoding in a HEAD response (Tuesday, 13 April)
Transfer-Encoding in a HEAD response (Sunday, 11 April)

William A. Rowe Jr.

Re: semantic equivalence of delimiters in URIs (Monday, 21 June)
Re: semantic equivalence of delimiters in URIs (Thursday, 17 June)
Re: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)
Re: Same resource exposed over HTTP and HTTPS (Thursday, 20 May)

Yngve N. Pettersen (Developer Opera Software ASA)

Re: Handling multiple headers when only one is allowed (Wednesday, 9 June)

Yngve Nysaeter Pettersen

Re: "actual content length", was: Handling multiple headers when only one is allowed (Friday, 11 June)

Yves Lafon

Re: proposal for issue #178 (Thursday, 3 June)
Re: proposal for issue #178 (Monday, 17 May)
Re: Clarification on use of Content-Location header (Thursday, 13 May)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Tuesday, 6 April)
Re: Issue 39: proposed example for varying the etag based on conneg (Friday, 2 April)

이문상

FW: I-D Submission: draft-lee-httpext-metadata-00.txt (Saturday, 26 June)

Last message date: Wednesday, 30 June 2010 21:03:01 UTC