ietf-http-wg@w3.org from October to December 2011 by subject

"Accept" on 415 responses?

#158: Proxy-Connection and Keep-alive

#160: Redirects and non-GET methods

#185: Location header payload handling

#186: Document HTTP's error-handling philosophy

#212: Refining Age for proxy chains

#231: Considerations for new headers

#255 and #299: Status code semantics

#274: Warn-code registry

#293: Interaction of request and response Cache-Control

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

#297: p1 7.2.4: retrying requests

#300: Define non-final responses

#306: does etag value really use quoted-string

#311: Denial of Service and Ranges

#312 (should there be a permanent variant of 307), was: I-D Action: draft-reschke-http-status-308-00.txt

#312: should there be a permanent variant of 307?

#314: realm parameter syntax

#318, was: Closing the connection

#320: add advice on defining auth scheme parameters

#321: Repeating auth-params

#322: Origin

#324: URI includes query

#327: Expect syntax

#327: Expect syntax, was: Prefer Draft Feedback

#329: header field considerations: quoted-string vs use of double quotes

202 Accepted, Location, and Retry-After

[#317] Cache-Control directive case sensitivity

[#319] Case sensitivity in p5

[#95] Multiple Content-Lengths

[apps-discuss] Discussion Place for CGI/1.1

[apps-discuss] Fwd: I-D Action: draft-nottingham-http-new-status-02.txt

[apps-discuss] I-D Action: draft-nottingham-http-new-status-02.txt

[apps-discuss] Partially fulfilled / draft-nottingham-http-new-status

[foaf-protocols] HTTP request header field for acceptable authentication methods

Additional HTTP Status Codes - "Request Too Onerous"

Additional HTTP Status Codes - draft-nottingham-http-new-status-02

best status code for bad auth method

Cache-Control directive case sensitivity

clarify some MUST requirements in HTTPbis part 1 section 3.3

Closing the connection

Comments on Section 6.1 (Persistent Connections) of HTTPbis Part 1, version 17

Content-Range on responses other than 206

Discussion Place for CGI/1.1

draft-ietf-httpbis-p1-messaging-16 1.2.1 ABNF Extension: #rule – Invalid example?

draft-snell-http-prefer

Feedback on draft-sigurdsson-anti-ddos-http-throttling

Feedback sought on timezone header for HTTP

Fwd: [Technical Errata Reported] RFC2616 (3056)

Fwd: I-D Action: draft-nottingham-http-new-status-02.txt

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

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

Fwd: Last Call: <draft-nottingham-http-new-status-03.txt> (Additional HTTP Status Codes) to Proposed Standard

Fwd: Re: Restoring PUT and DELETE

fya: Flickr: GirlieMac's stuff tagged with http

Getting to Last Call

HTTP header field syntax [WAS: Re: Prefer Draft Feedback]

HTTP request header field for acceptable authentication methods

httpbis -17 drafts

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

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

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

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

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

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

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

I-D Action: draft-nottingham-http-new-status-00.txt

I-D Action: draft-nottingham-http-new-status-02.txt

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

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

ID draft-petersson-forwarded-for-02.txt

IPV6 literal URL format mention might be useful

Is the ABNF for <request-target> in HTTPbis too general?

issue 11: URI includes query

Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs

issue 325: When are Location's semantics triggered?, was: Protocols/APIs and redirects

Issues addressed in the -17 drafts

json-string for HTTP header field parameter values

Last Call: <draft-nottingham-http-new-status-03.txt> (Additional HTTP Status Codes) to Proposed Standard

lower casing host names

Negotiated private cache storage allocation

New version of Memento Internet Draft

OAuth Bearer authentication - for proxies?

OT re HTTP auth disassocation of credentials

OWS before chunk

Partially fulfilled / draft-nottingham-http-new-status

Possible issue: Accept-language priority based on language order

Prefer Draft Feedback

Protocols/APIs and redirects

Proxy-Authorization with empty credentials

Restoring PUT and DELETE

RFC 2617 erratum

RFC5987bis parmsyntax, was: json-string for HTTP header field parameter values

SHOULD-level requirements in p6-caching

status code for header fields to big

Target maturity level for HTTPbis

The "Bearer" Authentication Scheme (draft-ietf-oauth-v2-bearer)

The priority of Content-Encoding and Content-Range

Unicode in HTTP headers (was Re: json-string for HTTP header field parameter values)

Last message date: Saturday, 31 December 2011 19:38:50 UTC

AltStyle によって変換されたページ (->オリジナル) /