ietf-http-wg@w3.org from January to March 2010 by subject

#147: header-specific canonicalisation

#197: Effect of CC directives on history lists

#204 (editorial): Clock requirement for caches

#29: correcting corrected_initial_age

#73: httpbis and deflate compression...

(Updating "content negotiation" language, issue 81), and TCN RFC 2295 to Proposed?

100 Continue and Expects

204 No Content for a resource which is known but has no representation yet?

3 short questions, Entity Tag & Content Location

300 Multiple Choices and safe methods

[410 Gone] HTTP/1.1, part 2: Message Semantics

[Fwd: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)]

[Fwd: WWW-Authenticate challenge for client-certificates]

[hybi] Long-polling to monitor resources

[OAUTH-WG] Authentication-Info Header

allowable characters in token as used in parameter ABNF

Amazon.com - Your Cancellation (495-265546-13651)

anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt

Authentication-Info Header

Cache behavior for authenticated contents

Clarification of http-409

Comment on draft-reschke-rfc2231-in-http-10 section 4.3

comments on draft-barth-mime-sniffing

Content Negotiation again

Content Sniffing impact on HTTPbis - #155

DRAFT Anaheim agenda

editorial LC comments on draft-nottingham-http-link-header-07.txt

Expect: 100-continue and proxies

exposing sensitive information in URIs - LC comments on draft-nottingham-http-link-header-07.txt

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

Fwd: New Version Notification - draft-nottingham-http-link-header-07.txt

Fwd: New Version Notification - draft-nottingham-http-link-header-08.txt

FYI: Anaheim IETF meeting

FYI: Google blog on Unicode

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

FYI: IETF LC for draft-reschke-rfc2231-in-http

FYI: review of draft-abarth-mime-sniff-03

httpbis and deflate compression...

HTTPbis Range header

HTTPbis Working Group meeting next Monday in Anaheim, CA

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

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

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

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

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

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

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

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

I-D ACTION:draft-ietf-httpbis-security-properties-04.txt

I-D ACTION:draft-ietf-httpbis-security-properties-05.txt

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

IETF77 meeting minutes

Issue 10, was: User interface requirements for redirecting to unsafe methods

issue 201, was: header parsing, trailing OWS

issue 202, was: Security considerations for DNS rebinding

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

Issue 43 (combining fragments)

Issues 43 and 185, was: Issue 43 (combining fragments)

Issues addressed in -09 drafts

Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard

Long-polling to monitor resources

Meeting plans re. Anaheim

Meeting plans re. Anaheim?

New Version Notification - draft-nottingham-http-link-header-07.txt

New version of Cache Context draft

no-cache response directive

one time passwords from private keys

p1-messaging proofreading

p2-semantics proofreading

p3-payload proofreading

p4-conditional proofreading

p5-range typo

p7-auth typo

parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt

Past Proposals for HTTP Auth Logout

proposal for issue #175 range flooding

proposal for issue #178

rel=meta and the Link Relation Type registry (was Re: New Version Notification - draft-nottingham-http-link-header-08.txt)

Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)

rev parameter - LC comment on draft-nottingham-http-link-header-07.txt

Review of third Last Call of Guidelines for Web Content Transformation Proxies

RFC 5789 on PATCH Method for HTTP

rfc2231-in-http: token characters, was: FYI: I-D Action:draft-reschke-rfc2231-in-http-08.txt

Security considerations for DNS rebinding

suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1

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

The meaning of rev

User interface requirements for redirecting to unsafe methods

W3C Account and HTMLWG Participation "Unlinked"

warning: redirect test cases broken, was: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)

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

Why do caching heuristics exclude 303?

WWW-Authenticate challenge for client-certificates

Last message date: Wednesday, 31 March 2010 23:00:26 UTC