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

"HTTP for Web Browsers and Servers"

(Re: issue #93) Duplicated headers and security vulnerabilities

307 Temporary Redirect

503, 403 & Retry-After: enforcing a limit on the number of requests allowed

ABNF conversion status (issue <http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36>)

Access Control for Cross-site Requests WD Published

An alterntive approach regarding i93: Repeating Single-value headers

BIS -02 Drafts

Books about HTTP "spirit"?

conditional request vs GET (new issue?)

CONNECT message including tunneled data

Connection limits

Content negotiation for request bodies

Content-* Semantics [i103]

Content-* Semantics [i103][i102]

Content-Disposition filename encoding

Content-Disposition filename encoding, was: IRIs, IDNAbis, and HTTP [i74]

Content-Length and 1xx status codes

Default charsets for text media types [i20]

Description section removed from charter?

does no-store request invalidate? [i23]

Fwd: I-D ACTION:draft-nottingham-http-link-header-01.txt

Fwd: i24: Requiring Allow in 405 responses

FYI: Firefox 3 beta 4 will enable pipelining over https

Header type defaulting [i104]

HTML5 vs content type sniffing

HTTP 2.0: Request from server to clients at persistent connection

http over sctp?

HTTPBis Summary

HttpOnly

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

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

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

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

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

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

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

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

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

I-D ACTION:draft-nottingham-http-link-header-01.txt

i107

i22: ETags on PUT responses

i24: Requiring Allow in 405 responses

i69: Clarify "Requested Variant"

i69: Clarify "Requested Variant" [was: New "200 OK" status codes, PATCH & PROPFIND]

i69: Requested Variant - moving forward

i74 proposal take 2

i74: Encoding for non-ASCII headers

i76: 305 Use Proxy

i93: Repeating Single-value headers

Indicating response errors after the status-line is sent

IRIs, IDNAbis, and HTTP

IRIs, IDNAbis, and HTTP (was: Reviving HTTP Header Linking: Some code and use-cases)

IRIs, IDNAbis, and HTTP [i74]

Is Content-Range extensible?

Javascript URI scheme (ACTION-46)

Link header field titles

Link header field titles (was: IRIs, IDNAbis, and HTTP)

NEW ISSUE(S): Retrying Requests

New issue: 15.3 misguided?

NEW ISSUE: message-body in CONNECT response

new issue: mismatch between RFC2616 and RFC4234 CHAR definition

NEW ISSUE: Monitoring Connections text

NEW ISSUE: weak validator: definition inconsistent

order of Accept-* and Server-Driven negotiation

OT: History (was: Re: Default charsets for text media types [i20])

PATCH vs multipart/byteranges vs Content-Range

Philidelphia

Pipelining problems [i99]

POWDER Use Case (was Re: Reviving HTTP Header Linking: Some code and use-cases)

PROCESS: Tracking design issues under discussion

Proposal: i105 Classification for Allow header

PROPOSAL: i24 Requiring Allow in 405 Responses

PROPOSAL: i74: Encoding for non-ASCII headers

PROPOSAL: i76 Use Proxy

PROPOSAL: i99 Pipelining Problems

PROPOSAL: Weak Validator definition [i101]

PUT, side effects and 201 Created? [ i21 ]

Reclassification of Allow as a response header

Reclassification of Allow as a response header [i105]

Request methods that allow an entity-body [i19]

Reviving HTTP Header Linking: Some code and use-cases

security impact of dropping charset default

security impact of dropping charset default [Re: text/* types and charset defaults [i20]]

Security Requirements for HTTP, draft -00

SRV records for HTTP

Suggestion for NEW Issue: Pipelining problems

text/* types and charset defaults

text/* types and charset defaults [i20]

Transfer-Encoding:chunked

Unknown and misplaced headers as entity headers

Unknown text/* subtypes

Unknown text/* subtypes [i20]

Updated Patch

UTF-8 (was: PROPOSAL: i74: Encoding for non-ASCII headers)

wildcards in digest auth domain field

Last message date: Monday, 31 March 2008 21:21:22 UTC