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

#122 (MIME-Version not listed in P1, general header fields)

#233 - Is * usable as a request-uri for new methods?

403 description clarifications

[#177] Realm required on challenges

[#193] Trailers and intermediaries

[#203] Max-forwards and extension methods

[#208] IANA registry for cache-control directives

[#232] User-Agent Guidelines (proposal)

[#95] Multiple Content-Lengths

[Fwd: I-D Action:draft-ietf-kitten-digest-to-historic-02.txt]

A note about the issues list and editorial workflow

Charter revision

Clarification on use of Content-Location header

Comments on draft-ietf-httpbis-content-disp-00.txt

conditional-request implementation feedback

disallowing userinfo in http and https URIs

DRAFT HTTPbis agenda for Maastricht

draft-bryan-metalinkhttp-18.txt

effective request URI/target URI, issues 221 & 222, was: Issues addressed by the -10 drafts

effective request URI/target URI, issues 221 & 222, was: Issues addressed, by the -10 drafts

Forcing validation

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

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

Fwd: I-D Action:draft-nottingham-http-portal-01.txt

Fwd: I-D Action:draft-reschke-basicauth-enc-00.txt

Fwd: I-D Action:draft-reschke-basicauth-enc-01.txt

Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.txt

Fwd: I-D Action:draft-reschke-rfc2183-in-http-03.txt

Fwd: Proposal for work on an efficient, browser-friendly, HTTP-based communication protocol for fine-grained information exchange

Fwd: RFC 5987 on Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters

how to handle "Not Yet Available"?

http URI grammar

HTTPbis -10 drafts published

HTTPbis -10 drafts published : Connection header

HTTPbis -11 drafts published

httpbis-p2 : 1xx messages may not always be treated as 100

I-D Action:draft-ietf-httpbis-content-disp-00.txt

I-D Action:draft-ietf-httpbis-content-disp-01.txt

I-D Action:draft-ietf-httpbis-content-disp-02.txt

I-D Action:draft-ietf-httpbis-method-registrations-04.txt

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

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

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

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

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

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

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

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

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

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

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

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

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

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

I-D Action:draft-loreto-http-timeout-00.txt

I-D Action:draft-nottingham-http-pipeline-00.txt

I-D Action:draft-nottingham-http-portal-00.txt

I-D Action:draft-reschke-rfc2183-in-http-03.txt [ new WG item ]

I-D Submission: draft-lee-httpext-metadata-00.txt

IANA hanges to draft-nottingham-http-link-header

IPR Disclosure: CNRS's Statement about IPR related to RFC 4768, RFC 2069, RFC 4169, and draft-ietf-httpbis-p7-auth-11

Issue 123 (factor out Content-Disposition), was: I-D Action:draft-ietf-httpbis-content-disp-00.txt

Issue 141: "should we have an auth scheme registry"

Issue 146, was: Users with different access rights in HTTP Authentication

Issue 160 (Redirects and non-GET methods)

Issue 195, was: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header

Issue 208, was: Issues addressed by the -10 drafts

issue 226, "proxies not supporting certain methods"

Issue 241 conditional header eval order, was: conditional-request implementation feedback

Issue 39, was: Issues addressed by the -10 drafts

issue 79: must understand content-* header fields or fail

Issue: expect 100-continue in HTTP/1.0 requests

Issues addressed by the -10 drafts

Issues addressed in the -10 and -11 drafts

Link Relation Registry initial contents

Migrating CONNECT and Upgrade details from RFC2817

Minutes for Maastricht

Multiple Content-Type headers (was: Re: [#95] Multiple Content-Lengths)

Multiple content-types, was: [#95] Multiple Content-Lengths

New issue: p5-range 5.4.2, proxy recommendations regarding 200 responses to Range

NEW: #223: Allowing heuristic freshness for new status codes

NEW: #224 - Header Classifications

NEW: #225: PUT and DELETE invalidation vs. staleness

NEW: #233 - Is * usable as a request-uri for new methods?

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

NEW: value space of status codes [#213]

No WG meeting at IETF 79

parsing decimals, was: HTTPbis -10 drafts published

parsing of unknown challenges, was: Ticket 237

POST with empty body

proposal for issue #178

Proposal for work on an efficient, browser-friendly, HTTP-based communication protocol for fine-grained information exchange

Protocol switch before, or after the 101 response?

Questions (errata?) about caching authenticated responses [#174]

Reminder: HTTPbis WG meeting today

remove/deprecate User-Agent header?

Request for feedback on HTTP Streaming overview (draft-wu-http-streaming-optimization-ps)

Revised Maastricht Agenda

rewritten section on Content-Location

rewritten section on message body and length

RFC 5987 on Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters

Scope of body in an OPTIONS response

sending Last-Modified in 304 and 206 responses

Specific non-2616 MS RFC implementation

ticket #78 (Relationship between 401, Authorization and WWW-Authenticate)

Ticket 237 (absorbing more of 2617), was: Minutes for Maastricht

Unifying & standardizing X-Moz & X-Purpose headers

User confirmation and 307 redirects

User confirmation and 307 redirects [#238]

WG Action: RECHARTER: Hypertext Transfer Protocol Bis (httpbis)

WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)

Last message date: Thursday, 30 September 2010 07:47:39 UTC