ietf-http-wg@w3.org from July to September 2008 by author

A. Rothman

must a partial response range be exact? (Wednesday, 24 September)
multipart/byteranges minimum number of parts (Wednesday, 24 September)

Adam Barth

Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)

Adrian Chadd

X-Forwarded-For and IPv6? (Wednesday, 27 August)

Adrien de Croy

Re: how to get traction on an I-D (Thursday, 11 September)
how to get traction on an I-D (Wednesday, 10 September)
Re: qvalue * (Monday, 4 August)
Re: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)

Alan Dean

Re: Review of Content Transformation Guidelines Last Call? (Friday, 29 August)

Alexey Melnikov

Re: https URI scheme (Sunday, 10 August)

Alfonso Martínez de Lizarrondo

Re: Microsoft's "I mean it" content-type parameter (Sunday, 6 July)

Amit Klein

(issue 100) - security considerations (Thursday, 18 September)
(issue 95) - security considerations (Thursday, 11 September)
(issue 77) - concrete security issues (Thursday, 11 September)
(issue 30) - concrete security-related examples (Thursday, 11 September)

Anne van Kesteren

Re: the "HTML URL" issue (Tuesday, 8 July)

Anthony Bryan

Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Saturday, 20 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-02) (Thursday, 4 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Wednesday, 3 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Wednesday, 3 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Wednesday, 3 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Tuesday, 2 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Tuesday, 2 September)
Metalink XML Download Description Format (draft-bryan-metalink-01) (Monday, 1 September)

Anton Blomberg

Serve page from different server without redirect (Monday, 15 September)

B.N. Kausik

Re: A proposal for Shared Dictionary Compression over HTTP (Tuesday, 9 September)

Bill de hOra

Re: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Saturday, 2 August)

Boris Zbarsky

Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)

Brian McBarron

Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Monday, 15 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 12 September)

Brian Smith

RE: A proposal for Shared Dictionary Compression over HTTP (Tuesday, 9 September)
XML namespace URIs for IETF specifications (was RE: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01)) (Tuesday, 2 September)
RE: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
RE: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
RE: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
RE: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
RE: Set-Cookie vs list header parsing (i129) (Wednesday, 27 August)
RE: HTTPS URI scheme (i128), was: https URI scheme (Wednesday, 27 August)
RE: Factoring out Content-Disposition (i123) (Tuesday, 19 August)
RE: Factoring out Content-Disposition (i123) (Monday, 18 August)
RE: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Monday, 18 August)
RE: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Monday, 18 August)
RE: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Sunday, 17 August)
RE: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Sunday, 17 August)
RE: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Friday, 15 August)
RE: Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers (Friday, 15 August)
RE: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Friday, 15 August)
RE: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Sunday, 10 August)
RE: "Variant" language in Content-Location (Issue 109) (Thursday, 7 August)
RE: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
RE: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
RE: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
RE: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Tuesday, 5 August)
RE: issue 85 - range unit extensions (Tuesday, 5 August)
RE: i107 (Friday, 1 August)
RE: i107 (Thursday, 31 July)
RE: i107 (Thursday, 31 July)
RE: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Thursday, 31 July)
RE: i107 (Thursday, 31 July)
RE: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
RE: PROPOSAL: Weak Validator definition [i101] (Tuesday, 29 July)
RE: i37: Vary and non-existant headers (Tuesday, 29 July)
RE: PROPOSAL: Weak Validator definition [i101] (Tuesday, 29 July)
RE: i107 (Tuesday, 29 July)
RE: i37: Vary and non-existant headers (Monday, 28 July)
RE: i107 (Monday, 28 July)
RE: i107 (Monday, 28 July)
RE: i107 (Monday, 28 July)

Charles Fry

Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 19 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Wednesday, 17 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Thursday, 28 August)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Monday, 21 July)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 18 July)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 18 July)

Chris Wilson

RE: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)

Dan Connolly

any error-free web pages at all? [was: Why Microsoft's authoritative=true won't work and is a bad idea] (Monday, 7 July)

Dan Winship

Re: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
Re: Set-Cookie vs list header parsing (i129) (Wednesday, 20 August)
Re: Set-Cookie vs list header parsing (i129) (Wednesday, 20 August)

Daniel Stenberg

Re: Set-Cookie vs list header parsing (i129) (Wednesday, 20 August)
Re: http implementations (Google Docs) (Sunday, 20 July)
RE: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Dave Cridland

Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Wednesday, 3 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Tuesday, 2 September)

Dave Kristol

Re: Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers (Friday, 15 August)
Re: Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers (Thursday, 14 August)

Dave Singer

Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

David Morris

Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)

Dominique Hazael-Massieux

Review of Content Transformation Guidelines Last Call? (Friday, 1 August)

Eric Lawrence

RE: Microsoft's "I mean it" content-type parameter (Sunday, 6 July)

Evgeniy Khramtsov

opaque parameter in the Authorization request header (Wednesday, 13 August)

Felix Sasaki

Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Saturday, 2 August)
Re: Proposed resolution for Issue 13 (language tags) (Wednesday, 30 July)

Frank Ellermann

Re: RFC2231 encoding in HTTP: whitespace handling (Thursday, 28 August)
Re: RFC2231 encoding in HTTP: whitespace handling (Thursday, 28 August)
Re: HTTPS URI scheme (i128) (Thursday, 28 August)
OT: historical file systems (was: Factoring out Content-Disposition (i123)) (Tuesday, 19 August)
Re: Factoring out Content-Disposition (i123) (Tuesday, 19 August)
Re: Factoring out Content-Disposition (i123) (Tuesday, 19 August)
Re: Factoring out Content-Disposition (i123) (Saturday, 16 August)
Re: Set-Cookie vs list header parsing (i129) (Saturday, 16 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Saturday, 16 August)
Re: Factoring out Content-Disposition (i123) (Saturday, 16 August)
Re: I-D Action:draft-reschke-rfc2231-in-http-00.txt (Friday, 15 August)
Re: opaque parameter in the Authorization request header (Wednesday, 13 August)
Re: https URI scheme (Sunday, 10 August)
Re: qvalue * (Tuesday, 5 August)
Re: qvalue * (Monday, 4 August)
Re: qvalue * (Monday, 4 August)
Re: qvalue * (Monday, 4 August)
Re: qvalue * (Monday, 4 August)
qvalue *, was: Re: Issue 113 (Monday, 4 August)
Re: qvalue *, was: Issue 113 (Monday, 4 August)
Re: Issue 113 (Monday, 4 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Sunday, 3 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Sunday, 3 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Saturday, 2 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Friday, 1 August)
Re: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)
Re: HTTPbis WG meeting tomorrow (Tue) (Tuesday, 29 July)
Re: issue 85 - range unit extensions (Monday, 28 July)
Re: issue 85 - range unit extensions (Monday, 28 July)
Re: HTTPbis WG meeting tomorrow (Tue) (Monday, 28 July)
Re: HTTP Enabled Location Delivery (HELD) (Tuesday, 22 July)
Re: Content-Disposition (new issue?) (Sunday, 20 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
Re: Microsoft's "I mean it" content-type parameter (Sunday, 6 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: New Version Notification for draft-nottingham-http-link-header-02 (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Wednesday, 2 July)

Geoffrey Sneddon

Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)

Henrik Nordstrom

Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
[New issue] Vary requirement level inconsistency (Sunday, 31 August)
RE: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
Re: Factoring out Content-Disposition (i123) (Sunday, 17 August)
Re: opaque parameter in the Authorization request header (Wednesday, 13 August)
Re: https URI scheme (Tuesday, 12 August)
Re: Strange "downref" to RFC2068 in description of 304 (new Issue 126) (Thursday, 7 August)
Re: "Variant" language in Content-Location (Issue 109) (Thursday, 7 August)
Re: "Variant" language in Content-Location (Issue 109) (Thursday, 7 August)
RE: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Thursday, 7 August)
Re: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Thursday, 7 August)
Re: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Thursday, 7 August)
Re: qvalue * (Tuesday, 5 August)
Re: qvalue * (Monday, 4 August)
Re: qvalue * (Monday, 4 August)
Re: qvalue * (Monday, 4 August)
Re: qvalue *, was: Re: Issue 113 (Monday, 4 August)
Re: qvalue *, was: Issue 113 (Monday, 4 August)
Re: Issue 113 (Monday, 4 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Monday, 4 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Sunday, 3 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Saturday, 2 August)
RE: i107 (Friday, 1 August)
RE: i107 (Thursday, 31 July)
RE: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Thursday, 31 July)
RE: i107 (Thursday, 31 July)
Re: i107 (Thursday, 31 July)
[new issue] p2 10.4 Location Content-Location reference (Thursday, 31 July)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Thursday, 31 July)
RE: i37: Vary and non-existant headers (Thursday, 31 July)
RE: i107 (Thursday, 31 July)
RE: i107 (Thursday, 31 July)
Re: i107 (Thursday, 31 July)
Re: Content-Disposition (new issue?) (Monday, 21 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
RE: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
RE: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: CONNECT (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: i28 proposed replacement text (Saturday, 5 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: i28 proposed replacement text (Wednesday, 2 July)
Re: i28 proposed replacement text (Wednesday, 2 July)

Henry S. Thompson

Re: URI/IRI vs HTML-URL (Tuesday, 8 July)

Ian Hickson

Re: A proposal for Shared Dictionary Compression over HTTP (Monday, 8 September)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)

IETF Drafts Team

Re: I-D candidate: draft-sharhalakis-httptz-04.txt (Monday, 29 September)

Internet-Drafts@ietf.org

I-D ACTION:draft-ietf-httpbis-method-registrations-00.txt (Tuesday, 9 September)
I-D Action:draft-ietf-httpbis-p6-cache-04.txt (Friday, 29 August)
I-D Action:draft-ietf-httpbis-p7-auth-04.txt (Friday, 29 August)
I-D Action:draft-ietf-httpbis-p3-payload-04.txt (Friday, 29 August)
I-D Action:draft-ietf-httpbis-p5-range-04.txt (Friday, 29 August)
I-D Action:draft-ietf-httpbis-p2-semantics-04.txt (Friday, 29 August)
I-D Action:draft-ietf-httpbis-p1-messaging-04.txt (Friday, 29 August)
I-D Action:draft-ietf-httpbis-p4-conditional-04.txt (Friday, 29 August)
I-D Action:draft-ietf-httpbis-security-properties-02.txt (Sunday, 13 July)

Jamie Lokier

Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 19 September)
Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Wednesday, 17 September)
Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: A proposal for Shared Dictionary Compression over HTTP (Tuesday, 9 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: Set-Cookie vs list header parsing (i129) (Wednesday, 20 August)
Re: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
Re: issue 85 - range unit extensions (Tuesday, 5 August)
Re: Namespace dispatching in XHTML, XML (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Jeff Currier

RE: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)
Re: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)
Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)

John Kemp

Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Jon Butler

Re: A proposal for Shared Dictionary Compression over HTTP (Wednesday, 10 September)
Re: A proposal for Shared Dictionary Compression over HTTP (Wednesday, 10 September)
Re: A proposal for Shared Dictionary Compression over HTTP (Wednesday, 10 September)

Jonathan Rees

Re: Fwd: New Version Notification for draft-nottingham-http-link-header-02 (Thursday, 17 July)

Julian Reschke

Re: Fwd: Status of Link header (Monday, 22 September)
Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 19 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Monday, 15 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Saturday, 13 September)
Re: Status of Link header (Friday, 12 September)
Re: Status of Link header (Friday, 12 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 12 September)
Issue 72 (method registry), was: I-D ACTION:draft-ietf-httpbis-method-registrations-00.txt (Wednesday, 10 September)
Re: A proposal for Shared Dictionary Compression over HTTP (Tuesday, 9 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Wednesday, 3 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Wednesday, 3 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Wednesday, 3 September)
IE8's content-type authoritative parameter moved into a separate response header (Wednesday, 3 September)
Re: XML namespace URIs for IETF specifications (was RE: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01)) (Tuesday, 2 September)
Content-Disposition in Google Chrome (Tuesday, 2 September)
Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01) (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Sunday, 31 August)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 29 August)
Re: planning publication of -04 drafts (Friday, 29 August)
Re: RFC2231 encoding in HTTP: whitespace handling (Thursday, 28 August)
Re: Set-Cookie vs list header parsing (i129) (Wednesday, 27 August)
Re: HTTPS URI scheme (i128), was: https URI scheme (Wednesday, 27 August)
RFC2231 encoding in HTTP: whitespace handling (Wednesday, 27 August)
Re: HTTPS URI scheme (i128), was: https URI scheme (Monday, 25 August)
planning publication of -04 drafts (Sunday, 24 August)
Re: HTTPS URI scheme (i128), was: https URI scheme (Friday, 22 August)
Re: Set-Cookie vs list header parsing (i129) (Thursday, 21 August)
Re: Set-Cookie vs list header parsing (i129) (Wednesday, 20 August)
Re: Factoring out Content-Disposition (i123) (Wednesday, 20 August)
Re: Set-Cookie vs list header parsing (i129) (Wednesday, 20 August)
Re: Factoring out Content-Disposition (i123) (Tuesday, 19 August)
Re: Factoring out Content-Disposition (i123) (Tuesday, 19 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Monday, 18 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Sunday, 17 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Saturday, 16 August)
Re: I-D Action:draft-reschke-rfc2231-in-http-00.txt (Saturday, 16 August)
Re: Factoring out Content-Disposition (i123) (Saturday, 16 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Saturday, 16 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Saturday, 16 August)
Re: Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers (Friday, 15 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Friday, 15 August)
Re: Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers (Friday, 15 August)
Re: Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers (Friday, 15 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Friday, 15 August)
Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Thursday, 14 August)
Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers (Wednesday, 13 August)
HTTPS URI scheme (i128), was: https URI scheme (Sunday, 10 August)
https URI scheme (Sunday, 10 August)
Re: issue 85 - range unit extensions (Friday, 8 August)
Re: issue 85 - range unit extensions (Friday, 8 August)
Re: Strange "downref" to RFC2068 in description of 304 (new Issue 126) (Thursday, 7 August)
Re: "Variant" language in Content-Location (Issue 109) (Wednesday, 6 August)
Re: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
Re: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
Re: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
Re: Strange "downref" to RFC2068 in description of 304 (new Issue 126) (Tuesday, 5 August)
Strange "downref" to RFC2068 in description of 304 (new Issue 126) (Tuesday, 5 August)
"Variant" language in Content-Location (Issue 109) (Tuesday, 5 August)
Re: issue 85 - range unit extensions (Tuesday, 5 August)
Re: issue 85 - range unit extensions (Tuesday, 5 August)
Re: qvalue * (Monday, 4 August)
Re: qvalue *, was: Re: Issue 113 (Monday, 4 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Monday, 4 August)
Re: qvalue *, was: Issue 113 (Monday, 4 August)
qvalue *, was: Issue 113 (Monday, 4 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Monday, 4 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Sunday, 3 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Saturday, 2 August)
Re: Issue 113, was: Proposed resolution for Issue 13 (language tags) (Friday, 1 August)
Issue 113, was: Proposed resolution for Issue 13 (language tags) (Friday, 1 August)
Re: Proposed patch for issue 71 (example for ETag matching) (Thursday, 31 July)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Thursday, 31 July)
Issue 125, was: [new issue] p2 10.4 Location Content-Location reference (Thursday, 31 July)
Re: Proposal: i67 - quoting charsets (Wednesday, 30 July)
Re: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)
Issue 124: "entity value" terminology, was: PROPOSAL: Weak Validator definition [i101] (Tuesday, 29 July)
Re: PROPOSAL: Weak Validator definition [i101] (Tuesday, 29 July)
Re: i37: Vary and non-existant headers (Tuesday, 29 July)
Re: PROPOSAL: Weak Validator definition [i101] (Tuesday, 29 July)
Re: PROPOSAL: Weak Validator definition [i101] (Tuesday, 29 July)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
Re: Proposed resolution for Issue 13 (language tags) (Tuesday, 29 July)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
Proposed patch for issue 71 (example for ETag matching) (Tuesday, 29 July)
Re: #106: vary header type (Tuesday, 29 July)
HTTPbis WG meeting tomorrow (Tue) (Monday, 28 July)
Re: Content-Disposition (new issue?) (Friday, 25 July)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 22 July)
HTTP Enabled Location Delivery (HELD) (Tuesday, 22 July)
Re: Content-Disposition (new issue?) (Sunday, 20 July)
Re: Content-Disposition (new issue?) (Sunday, 20 July)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Saturday, 19 July)
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 (Friday, 18 July)
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 (Tuesday, 15 July)
Re: Resolve issue 98? (Monday, 14 July)
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 (Saturday, 12 July)
Re: i28 proposed replacement text (Wednesday, 9 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
Re: URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
Issue 119, was: CONNECT (Monday, 7 July)
URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
CONNECT (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)
Re: i28 proposed replacement text (Saturday, 5 July)
Re: i28 proposed replacement text (Saturday, 5 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Wednesday, 2 July)
Re: i28 proposed replacement text (Wednesday, 2 July)
Microsoft's "I mean it" content-type parameter (Wednesday, 2 July)

Justin James

RE: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
RE: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
RE: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
RE: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
RE: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
RE: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
RE: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
RE: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Karl Dubost

Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)

Kris Zyp

Indicating acceptable request entity encodings (was Re: Support for compression in XHR?) (Wednesday, 10 September)
Re: issue 85 - range unit extensions (Wednesday, 3 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Sunday, 31 August)
Re: issue 85 - range unit extensions (Friday, 29 August)

L. David Baron

Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Lachlan Hunt

Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Larry Masinter

RE: issue 85 - range unit extensions (Friday, 8 August)

Lisa Dusseault

Re: how to get traction on an I-D (Thursday, 11 September)
Request for review and consensus -- draft-hartman-webauth-phishing (Wednesday, 3 September)
Re: issue 85 - range unit extensions (Wednesday, 6 August)

Mark Baker

Re: Status of Link header (Friday, 12 September)
Re: Review of Content Transformation Guidelines Last Call? (Wednesday, 13 August)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST (Tuesday, 29 July)
Namespace dispatching in XHTML, XML (Thursday, 3 July)

Mark Nottingham

Fwd: Status of Link header (Monday, 22 September)
Informal last call: stale-if-error, stale-while-revalidate (Monday, 22 September)
Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Wednesday, 17 September)
Dublin minutes (Wednesday, 17 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Wednesday, 17 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Wednesday, 17 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Monday, 15 September)
Re: X-Forwarded-For and IPv6? (Monday, 15 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Monday, 15 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Monday, 15 September)
Status of Link header (Friday, 12 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 12 September)
Re: A proposal for Shared Dictionary Compression over HTTP (Friday, 12 September)
Re: Content-Disposition in Google Chrome (Thursday, 4 September)
Re: Review of Content Transformation Guidelines Last Call? (Friday, 29 August)
Re: Review of Content Transformation Guidelines Last Call? (Friday, 29 August)
Re: Review of Content Transformation Guidelines Last Call? (Wednesday, 13 August)
Re: issue 85 - range unit extensions (Friday, 8 August)
Re: i37: Vary and non-existant headers (Tuesday, 29 July)
Re: i37: Vary and non-existant headers (Tuesday, 29 July)
Re: i107 (Tuesday, 29 July)
Re: issue 85 - range unit extensions (Monday, 28 July)
Re: i107 (Monday, 28 July)
Re: i107 (Monday, 28 July)
#106: vary header type (Monday, 28 July)
i37: Vary and non-existant headers (Monday, 28 July)
Re: issue 85 - range unit extensions (Monday, 28 July)
Re: i107 (Monday, 28 July)
PROPOSAL - i109: Clarify entity / representation / variant terminology (Monday, 28 July)
issue 85 - range unit extensions (Monday, 28 July)
Re: http implementations (Google Docs) (Sunday, 20 July)
Re: http implementations (Google Docs) (Sunday, 20 July)
http implementations (Google Docs) (Sunday, 20 July)
Re: Resolve issue 98? (Monday, 14 July)
Re: Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79 (Monday, 14 July)
Draft Dublin HTTPbis agenda (Tuesday, 8 July)
Fwd: I-D Action:draft-jennings-http-srv-00.txt (Monday, 7 July)
Fwd: New Version Notification for draft-nottingham-http-link-header-02 (Thursday, 3 July)

Martin Duerst

RE: issue 85 - range unit extensions (Wednesday, 27 August)
RE: issue 85 - range unit extensions (Friday, 22 August)
Re: URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)

Michael A. Puls II

Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)

Paul Hoffman

Re: https URI scheme (Sunday, 10 August)

Peter Gutmann

Re: [saag] Request for review and consensus -- draft-hartman-webauth-phishing (Thursday, 4 September)

Phil Archer

Re: Fwd: New Version Notification for draft-nottingham-http-link-header-02 (Thursday, 3 July)

Philip TAYLOR (Ret'd)

Re: any error-free web pages at all? [was: Why Microsoft's authoritative=true won't work and is a bad idea] (Monday, 7 July)

Robert Brewer

RE: issue 85 - range unit extensions (Wednesday, 3 September)
RE: issue 85 - range unit extensions (Monday, 1 September)
RE: "Variant" language in Content-Location (Issue 109) (Tuesday, 5 August)
RE: qvalue * (Monday, 4 August)
RE: qvalue * (Monday, 4 August)
RE: i28 proposed replacement text (Saturday, 5 July)

Robert Collins

Re: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)
Re: Microsoft's "I mean it" content-type parameter (Wednesday, 2 July)

Robert J Burns

Re: URI/IRI vs HTML-URL, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)

Roy T. Fielding

Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions (Friday, 19 September)
Re: issue 85 - range unit extensions (Tuesday, 2 September)
Re: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
Re: HTTPS URI scheme (i128), was: https URI scheme (Wednesday, 27 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Friday, 15 August)
Re: Quota Enforcement and the communication of violations of policy using HttpStatusCode's. (Tuesday, 29 July)
Re: i37: Vary and non-existant headers (Tuesday, 29 July)
Re: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

ryah dahl

Re: qvalue * (Monday, 4 August)

Sam Ruby

Re: Why Microsoft's authoritative=true won't work and is a bad idea (Monday, 7 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Sunday, 6 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Re: Why Microsoft's authoritative=true won't work and is a bad idea (Saturday, 5 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
RE: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Shane McCarron

Re: Status of Link header (Friday, 12 September)
Re: Status of Link header (Friday, 12 September)

Stefan Eissing

Re: [google-gears-eng] Re: Deploying new expectation-extensions (Tuesday, 16 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Monday, 15 September)
Re: "Variant" language in Content-Location (Issue 109) (Wednesday, 6 August)
Re: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
Re: the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea (Tuesday, 8 July)
Re: Microsoft's "I mean it" content-type parameter (Monday, 7 July)

Stefanos Harhalakis

I-D candidate: draft-sharhalakis-httptz-04.txt (Sunday, 21 September)

Stephane Bortzmeyer

Re: Request for review and consensus -- draft-hartman-webauth-phishing (Thursday, 11 September)

T.V Raman

Re: any error-free web pages at all? [was: Why Microsoft's authoritative=true won't work and is a bad idea] (Tuesday, 8 July)

Wei-Hsin Lee

A proposal for Shared Dictionary Compression over HTTP (Monday, 8 September)

William A. Rowe, Jr.

Re: [google-gears-eng] Re: Deploying new expectation-extensions (Wednesday, 17 September)
Re: [google-gears-eng] Re: Deploying new expectation-extensions (Wednesday, 17 September)
Re: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
Re: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
Re: Factoring out Content-Disposition (i123) (Tuesday, 19 August)
Re: Factoring out Content-Disposition (i123) (Tuesday, 19 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Saturday, 16 August)
Re: Factoring out Content-Disposition (i123) (Saturday, 16 August)
Re: Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?) (Friday, 15 August)
Re: qvalue * (Monday, 4 August)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Friday, 4 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)
Re: Microsoft's "I mean it" content-type parameter (Thursday, 3 July)

Yves Lafon

Re: A proposal for Shared Dictionary Compression over HTTP (Wednesday, 10 September)
Re: A proposal for Shared Dictionary Compression over HTTP (Wednesday, 10 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: issue 85 - range unit extensions (Monday, 1 September)
Re: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
RE: Set-Cookie vs list header parsing (i129) (Thursday, 28 August)
RE: issue 85 - range unit extensions (Wednesday, 27 August)
RE: issue 85 - range unit extensions (Wednesday, 27 August)
RE: Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109)) (Wednesday, 6 August)
Re: issue 85 - range unit extensions (Tuesday, 5 August)
Re: issue 85 - range unit extensions (Tuesday, 5 August)
Re: Issue 113 (Monday, 4 August)
RE: i107 (Friday, 1 August)
Re: i28 proposed replacement text (Wednesday, 2 July)

Last message date: Monday, 29 September 2008 16:44:17 UTC