from October to December 2007 by subject

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

209 No Content vs. application/empty

[Fwd: Working Group Last Call: draft-melnikov-digest-to-historic-00.txt]

[i16] Remove 'identity' token references

[i47] inconsistency in date format explanation

[i81] Content Negotiation for media types

[NEW ISSUE] Content-Length and Transfer-Encoding: security implications

[NEW ISSUE] Content-Length is a hop-to-hop header

[new issue] If(-None)-Match still refers to entity

[new issue] Re: Proxying OPTIONS *

Accepting pre-existing errata resolutions

Agenda updated

cacheability of status 303

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

conditional request vs GET (new issue?)

Connection: "close" — Case sensitive or not?

Content-Location as Base URI

Creating a HTTP "protocol feature set"

Custom Ranges

does no-store request invalidate?

Does Reason-Phrase allow LWS?

Draft minutes for Vancouver

draft-lafon-rfc2616bis-04 submitted, was: What to include into draft-lafon-rfc2616bis-04

draft-sayre-http-security-variance-00.txt, was: Straw-man charter for http-bis -- call for errata/clarifications to 2617

Editorial Nit: referring to status codes

HTTPBIS - getting started

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

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

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

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

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

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

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

i15: How to tell if a client does not support persistent connections

I18N and basic authentication

i25 - Accept-Encoding BNF [was: Erratum in RFC 2616]

i31 (qdtext BNF) resolved

i37 - Vary and non-existant headers

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

i70: cacheability of status 303

i88: 205 Bodies

i89: If(-None)-Match still refers to entity

i90: status of multipart/byteranges

i93: Repeating Single-value headers

Intro to Methods making Host header requirement

Issue 27 (PUT Idempotency)

Issues List -- new location

Link Header draft

moving forward with partitioned drafts

NEW ISSUE: cacheability of status 303

NEW ISSUE: Content-Coding vs ETags

NEW ISSUE: empty Host header

NEW ISSUE: message-body in CONNECT response

NEW ISSUE: Monitoring Connections text

NEW ISSUE: NO default charset

NEW ISSUE: normative references

NEW ISSUE: rel_path not used

new issue: remove redundant MUST obey xrefs

NEW ISSUE: repeating non-list-type-headers

NEW ISSUE: status of multipart/byteranges

NEW ISSUE: Transfer-Encoding in 1.0 messages

new issue: URI length limitations

NEW ISSUE: weak validator: definition inconsistent

NOTE WELL - contributions to this mailing list

Objectives of RFC2616bis?

Preliminary agenda up

progress on BNF conversion

Proxying OPTIONS *

References (was: Intro to Methods making Host header requirement)

request for feedback: RFC2616 BNF name collisions

Request for review on Access Control for Cross-site Requests

Request methods that allow an entity-body

Request methods that allow an entity-body [i19]

revised draft-decroy-http-progress-03

RFC 2616, partitioned

RFC 2617 Authentication-Info BNF

RFC2616 erratum "languagetag"

RFC2617: section reference erratum

semantic error in RFC 2616

Semantic meaning of double quotation marks delimiting quoted-string

SRV records in scope? (Was: WG Review: HyperText Transport Protocol Bis (httpbis)

status of delta compression (encoding) for HTTP servers/browsers?

status on partitioned drafts

Status, Vancouver

Unknown text/* subtypes

Unknown text/* subtypes (was: Request for review of Turtle (an RDFserialization) media type: text/turtle)

Updated PATCH draft

Using server-driven negotiation

Vancouver agenda item BNF, was: progress on BNF conversion

Vancouver agenda topics

Via MUST discussion

Via MUST discussion [was: Re: status on partitioned drafts

WG Action: Hypertext Transfer Protocol Bis WG (httpbis)

WG drafts for partitioned 2616bis

WG Review: HyperText Transport Protocol Bis (httpbis)

What to include into draft-lafon-rfc2616bis-04, was: Vancouver agenda topics

Working Group Last Call: draft-melnikov-digest-to-historic-00.txt

Last message date: Saturday, 29 December 2007 16:57:55 UTC