from January to March 2009 by subject

-06 drafts, was: HTTPbis status

[oauth] OAuth and HTTP proxies

[W3C BPWG] HTTP header fields X-* and normal ones / question

A question about Content-Length header

A question about Content-Length header & Transfer Coding

ABNF conversiov (issue 36), was: HTTPbis status

Cache key history

case-sensitivity of weakness indicator

CERT VU#435052 - intercepting proxy vulnerability

Clarifying Content-Location for POST/PUT/other methods, was: Cache key history (see also issue 136)

Coming to a conclusion on draft-abarth-origin

comments on caching rewrite

comments on draft-nottingham-http-link-header-04

Content-Location, was: PATCH draft

Cookie-based HTTP Authentication (draft-broyer-http-cookie-auth-00)

Correct status code for unknown transfer-encoding

Definition of 'resource' not consistent with RFC 3986

Empty host in 'http' scheme

Extension headers and caching

Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03

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

Fwd: I-D Action:draft-roach-sip-http-subscribe-00.txt

FYI: Link -04

GET/HEAD support "MUST"

HTTPbis meeting agenda, participation details

HTTPbis status

HTTPOnly Cookies Specification

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

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

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

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

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

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

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

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

i58: What identifies an HTTP resource

Issue 152: range unit in Range header for custom ranges, was: issue 85 - range unit extensions

issue 85 - range unit extensions

Keep-alive header in RFC2616

link relationship registration

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

Minutes from informal IETF/W3C meeting about HTML5 work

multipart/byteranges - was A question about Content-Length header

New issue: Clarify when Referer is sent #144

NEW ISSUE: content sniffing

NEW ISSUE: Drop Content-Location

NEW ISSUE: isolate TCP-specific aspects of HTTP

New mailing list: hybi (HTTP "long poll" and related protocols)

Nit in section 2.1.1 of httpbis-p1

OAuth and HTTP proxies

Origin header for safe methods other than GET/HEAD, was: The HTTP Origin Header (draft-abarth-origin)

Origin vs Authority; use of HTTPS (draft-nottingham-site-meta-01)

p6-caching: commentary from -05 to -06

PATCH draft

Pipelining in HTTP 1.1

PROPOSAL - i109: Clarify entity / representation / variant terminology

Proposal: 3xx (Unauthorized, See Other) status

Providing two-way communication back to a server from a Web page

Referer URI MUST NOT include a fragment

Request for feedback: HTTP-based Resource Descriptor Discovery

required behaviour of client when abortive disconnect

Retry-After header on 20X response -- HTTP/1.1 spec extension?

Review of Content-Encoding: value token

Status of RFC 2295: Transparent Content Negotiation in HTTP (Experimental)

Status update / San Francisco meeting / etc.

The HTTP Origin Header (draft-abarth-origin)

Two new IDs of relevance to this working group

URI handling for Location

Use of Link rel+type for application discovery

Users with different access rights in HTTP Authentication

Weak ETag handling

Last message date: Tuesday, 31 March 2009 22:03:22 UTC