ietf-http-wg@w3.org from April to June 2011 by subject

#117: cache invalidation upon update

#186: Document HTTP's error-handling philosophy

#20: Default charsets for text media types

#231: Considerations for new headers

#273: HTTP-Version should be redefined as fixed length pair of DIGIT . DIGIT

#282: Recommend minimum sizes for protocol elements

#283: Set expectations around buffering

#285: Strength of requirements on Accept re: 406

#288: Considering messages in isolation

#289: "understanding" methods

#289: SHOULD-level requirements in p6-caching

#290 [was: SHOULD-level requirements in p6-caching]

#291: Cache Extensions can override no-store, etc.

#292: Pragma

#295: Applying original fragment to "plain" redirected URI (also #43)

#296: 203 Non-Authoritative Information: deprecate?

#297: p1 7.2.4: retrying requests

203 Non-Authoritative Information: deprecate?

9.9 CONNECT (Re: 203 Non-Authoritative Information: deprecate?)

[#38] httpbis-p6-cache-14, and vary headers

[apps-discuss] [OAUTH-WG] [http-state] HTTP MAC Authentication Scheme

[apps-discuss] HTTP MAC Authentication Scheme

[Fwd: Document Action: 'Moving DIGEST-MD5 to Historic' to Informational RFC (draft-ietf-kitten-digest-to-historic-04.txt)]

[Fwd: I-D Action: draft-melnikov-mime-default-charset-00.txt]

[http-state] [apps-discuss] HTTP MAC Authentication Scheme

[OAUTH-WG] [http-state] [apps-discuss] HTTP MAC Authentication Scheme

[TLS] Revised TLS Charter

ABNF for Authorization header not quite right

About draft-nottingham-http-pipeline-01.txt

API Rate Limits and HTTP Code [#255]

BCP for returning HTTP Authentication (2617) Error Status (questions from the OAuth WG)

Clarifying Pragma's introduction

Content-Disposition status

Denial of Service using invalid Content-Length header

Discussion of Blob URI Scheme for Binary Data Access | IETF

DNT Header RFC

Fwd: HTTPBIS - Requested session has been scheduled for IETF 81

Fwd: I-D Action: draft-nottingham-http-browser-hints-00.txt

Fwd: I-D Action: draft-nottingham-linked-cache-inv-00.txt

Fwd: I-D Action:draft-reschke-rfc5987bis-00.txt

Fwd: IESG Statement on Designating RFCs as Historic [#254]

Fwd: RFC 6202 on Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP

Fwd: RFC 6266 on Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)

Fwd: Second Last Call: <draft-hammer-hostmeta-16.txt> (Web Host Metadata) to Proposed Standard

Heuristics and "negative caching"

HTTP Draft-p1 and http scheme definition

HTTP MAC Authentication Scheme

httpbis -14 drafts

httpbis-p6-cache-14, and vary headers

I-D Action: draft-nottingham-http-browser-hints-00.txt

I-D Action: draft-nottingham-linked-cache-inv-00.txt

I-D ACTION:draft-ietf-httpbis-authscheme-registrations-01.txt

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

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

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

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

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

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

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

I-D Action:draft-reschke-rfc5987bis-00.txt

I-D draft-petersson-forwarded-for-00.txt

If-Range and cache validation using Last-Modified

IPv6 and draft-petersson-forwarded-for

Issue 178 (Content-MD5), was: Prague Minutes

Issues addressed in the -14 drafts

Last Call for HTML5 in the W3C

Location, fragments, and when not to use them

Media Fragments spec and HTTP

New version of Memento I-D

New version of the Memento Internet Draft

NEW: #235: Cache Invalidation only happens upon successful responses

On the abuse of chunking for interactive usages

p1 7.2.4: retrying requests

p6 -14 version and ticket #274

p6-cache-13; max-age typo, editorial inconsistency

Possible erratum in Part 1, section 9.4.

Prague Minutes

Privacy and HTTP intermediaries

PUT and DELETE methods in 200 code

Quebec City

Realm requirements (issue 177)

Redirects and headers

RFC 6266 on Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)

SHOULD-level requirements in p6-caching

status code for header fields to big

Talking HTTPS to proxies

Ticket #294, was: 403 description clarifications

Whitespace before responses

Last message date: Thursday, 30 June 2011 23:34:42 UTC