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

"actual content length", was: Handling multiple headers when only one is allowed

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

#168: understanding CC directives

#73: httpbis and deflate compression...

'Age' for web pages

100 Continue and Expects

3 short questions, Entity Tag & Content Location

300 Multiple Choices and safe methods

304 updating ETag

[#211] Query string cacheability

[CSAIL #48586] AutoReply: Re: Message received

[CSAIL #48734] AutoReply: Message received

[http-state] Missing specification in RFC 2617, cannot use a user name nor a password in encoding different from ISO-8859-1

[new issue] p1 messaging 4.2. fails to account for requested scheme which impacts http compared to https

Age response header and HTTP/1.0 requests

Broken link

Cache behavior for authenticated contents

clarification of 7.2.2. Monitoring Connections for Error Status Messages

Clarification on use of Content-Location header

clarity needed for browser behaviors when receiving 206 status codes

Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")

Duplicating request component in an HTTP authentication scheme

Expect: 100-continue and proxies

Explicit instructions on use of fragment in request URI

Fwd: [http-state] WG Last Call for draft-ietf-httpstate-cookie-08 ?

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

Fwd: I-D Action:draft-ietf-core-coap-00.txt

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

Fwd: I-D Action:draft-nottingham-http-link-header-09.txt

Fwd: RFC 5861 on HTTP Cache-Control Extensions for Stale Content

FYI Cache-control deployment

Handling multiple headers when only one is allowed

How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)

HTTP Application Security (HAS) BoF

http progress notification

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

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

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

IETF BoF @IETF-78 Maastricht: HASMAT - HTTP Application Security Minus Authentication and Transport

In support of sending fragment IDs to the server (issue #43)

is rfc2616 the right document to study

Issue 101, was: Issue 39: proposed example for varying the etag based on conneg

Issue 163, was: Meaning of invalid but well-formed dates

Issue 165, was: Issue 163, was: Meaning of invalid but well-formed dates

Issue 196, was: #110: how to determine what entity a response carries

Issue 200 ("word" in ABNF), was: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1

Issue 209, was: [new issue] p1 messaging 4.2. fails to account for requested scheme which impacts http compared to https

Issue 39: proposed example for varying the etag based on conneg

Labs/Weave/Identity/Account Manager/Spec/Latest - MozillaWiki

Managing multiple authorities, resources and representations

Missing specification in RFC 2617, cannot use a user name nor a password in encoding different from ISO-8859-1

Multiple challenges in a single WWW-Authenticate header field

NEW: value space of status codes [#213]

one time passwords from private keys

pack200-gzip Content Coding

preparing new drafts for IETF 78

proposal for issue #175 range flooding

proposal for issue #178

Protocol Action: 'Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters' to Proposed Standard

Query string cacheability

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

Revisiting Retry-After w/ 202

Revitalizing Caching ✩ Mozilla Hacks – the Web developer blog

Same resource exposed over HTTP and HTTPS

semantic equivalence of delimiters in URIs

short-time client side caching and clock skew

short-time client side caching and clock skew [#212]

TAG requests addition to section 3.2.1 of Part 3 [#155]

Ticket 183: "requested resource" in content-encoding definition

ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content

Transfer-Encoding in a HEAD response

update: http progress notification

What are "appropriate Cache-Control or Expires header fields"

Last message date: Wednesday, 30 June 2010 21:03:01 UTC