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

"Variant" language in Content-Location (Issue 109)

#106: vary header type

(issue 100) - security considerations

(issue 30) - concrete security-related examples

(issue 77) - concrete security issues

(issue 95) - security considerations

[APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01)

[APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-02)

[gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions

[google-gears-eng] Re: Deploying new expectation-extensions

[new issue] p2 10.4 Location Content-Location reference

[New issue] Vary requirement level inconsistency

[saag] Request for review and consensus -- draft-hartman-webauth-phishing

A proposal for Shared Dictionary Compression over HTTP

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

CONNECT

Content-Disposition (new issue?)

Content-Disposition in Google Chrome

Deprecate Content-Location? (was RE: "Variant" language in Content-Location (Issue 109))

Draft Dublin HTTPbis agenda

Dublin minutes

Factoring out Content-Disposition (i123)

Factoring out Content-Disposition (i123), was: Content-Disposition (new issue?)

Fwd: I-D Action:draft-jennings-http-srv-00.txt

Fwd: New Version Notification for draft-nottingham-http-link-header-02

Fwd: Status of Link header

how to get traction on an I-D

HTTP Enabled Location Delivery (HELD)

http implementations (Google Docs)

HTTPbis WG meeting tomorrow (Tue)

https URI scheme

HTTPS URI scheme (i128)

HTTPS URI scheme (i128), was: https URI scheme

I-D ACTION:draft-ietf-httpbis-method-registrations-00.txt

I-D Action:draft-ietf-httpbis-p1-messaging-04.txt

I-D Action:draft-ietf-httpbis-p2-semantics-04.txt

I-D Action:draft-ietf-httpbis-p3-payload-04.txt

I-D Action:draft-ietf-httpbis-p4-conditional-04.txt

I-D Action:draft-ietf-httpbis-p5-range-04.txt

I-D Action:draft-ietf-httpbis-p6-cache-04.txt

I-D Action:draft-ietf-httpbis-p7-auth-04.txt

I-D Action:draft-ietf-httpbis-security-properties-02.txt

I-D Action:draft-reschke-rfc2231-in-http-00.txt

I-D candidate: draft-sharhalakis-httptz-04.txt

i107

i28 proposed replacement text

i37: Vary and non-existant headers

IE8's content-type authoritative parameter moved into a separate response header

Indicating acceptable request entity encodings (was Re: Support for compression in XHR?)

Informal last call: stale-if-error, stale-while-revalidate

Issue 113

Issue 113, was: Proposed resolution for Issue 13 (language tags)

Issue 119, was: CONNECT

Issue 124: "entity value" terminology, was: PROPOSAL: Weak Validator definition [i101]

Issue 125, was: [new issue] p2 10.4 Location Content-Location reference

Issue 72 (method registry), was: I-D ACTION:draft-ietf-httpbis-method-registrations-00.txt

Issue 72, was: Status of IANA Considerations (registrations and registries) -- issues 40, 59, 72, 79

Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST

issue 85 - range unit extensions

Metalink XML Download Description Format (draft-bryan-metalink-01)

Microsoft's "I mean it" content-type parameter

multipart/byteranges minimum number of parts

must a partial response range be exact?

Namespace dispatching in XHTML, XML

New Version Notification for draft-nottingham-http-link-header-02

opaque parameter in the Authorization request header

OT: historical file systems (was: Factoring out Content-Disposition (i123))

planning publication of -04 drafts

PROPOSAL - i109: Clarify entity / representation / variant terminology

Proposal: i67 - quoting charsets

PROPOSAL: Weak Validator definition [i101]

Proposed patch for issue 71 (example for ETag matching)

Proposed resolution for Issue 13 (language tags)

Quota Enforcement and the communication of violations of policy using HttpStatusCode's.

qvalue *

qvalue *, was: Issue 113

qvalue *, was: Re: Issue 113

Request for review and consensus -- draft-hartman-webauth-phishing

Resolve issue 98?

Review of Content Transformation Guidelines Last Call?

RFC2231 encoding in HTTP: whitespace handling

Serve page from different server without redirect

Set-Cookie vs list header parsing (i129)

Set-Cookie vs list header parsing (i129), was: NEW ISSUE: repeating non-list-type-headers

Status of Link header

Strange "downref" to RFC2068 in description of 304 (new Issue 126)

the "HTML URL" issue

the "HTML URL" issue, was: Why Microsoft's authoritative=true won't work and is a bad idea

URI/IRI vs HTML-URL

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

Why Microsoft's authoritative=true won't work and is a bad idea

X-Forwarded-For and IPv6?

XML namespace URIs for IETF specifications (was RE: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01))

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