Tuesday, 30 June 2009
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: Content-MD5 and partial responses
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: Content-MD5 and partial responses
- Re: Content-MD5 and partial responses
Monday, 29 June 2009
- Re: httpbis-p6-cache-06 and no-store response directive
- Appropriate response code if server wants to enforce conditional PUT/DELETE?
- Content-MD5 and partial responses
- Re: httpbis-p6-cache-06 and no-store response directive
Sunday, 28 June 2009
- The HTTP Sec-From Header (draft-abarth-origin)
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
Friday, 26 June 2009
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: CR and LF in chunk extension values
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: HTTP over SCTP without chunked encoding
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: HTTP over SCTP without chunked encoding
- Re: HTTP over SCTP without chunked encoding
Thursday, 25 June 2009
- Re: HTTP over SCTP without chunked encoding
- Re: draft-nottingham-http-link-header-05: a question and an experimental implementation
- Re: draft-nottingham-http-link-header-05: a question and an experimental implementation
- Re: draft-nottingham-http-link-header-05: a question and an experimental implementation
- Re: httpbis-p6-cache-06 and no-store response directive
- Fwd: Questions (errata?) about caching authenticated responses [#174]
- Re: i37: Vary and non-existant headers
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: CR and LF in chunk extension values
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: PROPOSAL: Sending Referer [#144]
- Re: RED: a tool for examining HTTP resources
- RED: a tool for examining HTTP resources
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: HTTP over SCTP without chunked encoding
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
Wednesday, 24 June 2009
- Re: Review of Content-Encoding: value token
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: The HTTP Origin Header (draft-abarth-origin)
- Re: Proposal for i23: no-store invalidation
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: 304 reponse with unrecognised ETag
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
Tuesday, 23 June 2009
- Re: draft-nottingham-http-link-header-05: a question and an experimental implementation
- Re: draft-nottingham-http-link-header-05: a question and an experimental implementation
Monday, 22 June 2009
Sunday, 21 June 2009
Friday, 19 June 2009
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- 304 reponse with unrecognised ETag
- draft-nottingham-http-link-header-05: a question and an experimental implementation
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
Thursday, 18 June 2009
- Re: Content Sniffing impact on HTTPbis - #155
- Re: comments on draft-barth-mime-sniffing
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: Content Sniffing impact on HTTPbis - #155
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: HTTP/1.1 CONNECT request without Host header
- Re: chunking without chunking
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: comments on draft-barth-mime-sniffing
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: httpbis-p6-cache-06 and no-store response directive
Wednesday, 17 June 2009
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- CR and LF in chunk extension values
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: HTTP/1.1 CONNECT request without Host header
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: HTTP/1.1 CONNECT request without Host header
- Re: comments on draft-barth-mime-sniffing
- Re: chunking without chunking (MSIE8 and Chrome issues?)
- chunking without chunking
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: Content Sniffing impact on HTTPbis - #155
- Re: HTTP/1.1 CONNECT request without Host header
- Re: HTTP/1.1 CONNECT request without Host header
- Re: HTTP/1.1 CONNECT request without Host header
- Re: HTTP/1.1 CONNECT request without Host header
- Re: HTTP/1.1 CONNECT request without Host header
- Re: comments on draft-barth-mime-sniffing
Tuesday, 16 June 2009
- Re: HTTP/1.1 CONNECT request without Host header
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- HTTP/1.1 CONNECT request without Host header
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- FYI: HTTPbis Tweets
- "Resource" in dictionaryRe: Content Sniffing impact on HTTPbis - #155
Monday, 15 June 2009
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: httpbis-p6-cache-06 and no-store response directive
- Review of new HTTPbis text for 303 See Other
- Re: Is OPTIONS Safe?
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: comments on draft-barth-mime-sniffing
Sunday, 14 June 2009
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
Saturday, 13 June 2009
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Is OPTIONS Safe?
- Re: 10 years
- #94 (Reason-Phrase BNF)
- 10 years
- Re: Proposal: Is OPTIONS Safe? [#171]
- Re: Content Sniffing impact on HTTPbis - #155
- Re: PROPOSAL: Sending Referer [#144]
- Re: PATCH and ETags
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
Friday, 12 June 2009
- RE: Content Sniffing impact on HTTPbis - #155
- Re: PROPOSAL: Sending Referer [#144]
- Re: Sending Referer [#144]
- Re: Sending Referer [#144]
- Re: Content Sniffing impact on HTTPbis - #155
- PATCH and ETags
- Re: PROPOSAL: Sending Referer [#144]
- Re: Sending Referer [#144]
- Re: Sending Referer [#144]
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: comments on draft-barth-mime-sniffing
- Re: non CHAR characters in headers
- Re: non CHAR characters in headers
- non CHAR characters in headers
- Re: HTTP Batch Request Draft
- PROPOSAL: Sending Referer [#144]
- Re: PROPOSAL: Content Sniffing impact on HTTPbis - #155
Thursday, 11 June 2009
- Fwd: [hybi] draft-loreto-http-bidirectional
- Add: Re: How legal is this HTTP header (1.1)?
- Re: How legal is this HTTP header (1.1)?
- Re: How legal is this HTTP header (1.1)?
- Re: Add: How legal is this HTTP header (1.1)?
- Re: Add: How legal is this HTTP header (1.1)?
- Re: Requests that do now allow bodies (do they exist?), was: Proposal: 205 Bodies [#88]
- Re: Add: How legal is this HTTP header (1.1)?
- Requests that do now allow bodies (do they exist?), was: Proposal: 205 Bodies [#88]
- Add: How legal is this HTTP header (1.1)?
- How legal is this HTTP header (1.1)?
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal for i23: no-store invalidation
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal for i23: no-store invalidation
Wednesday, 10 June 2009
- Re: Proposal for i23: no-store invalidation
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal for i23: no-store invalidation
- Re: HTTP Batch Request Draft
- Re: HTTP Batch Request Draft
- Re: HTTP Batch Request Draft
Tuesday, 9 June 2009
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal for i23: no-store invalidation
- Re: Proposal for i23: no-store invalidation
- Re: Proposed Erratum for RFC 2817, was: Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
- Revised: Upcoming meetings (Stockholm and Hiroshima)
Monday, 8 June 2009
- Re: HTTP Batch Request Draft
- Re: HTTP Batch Request Draft
- Re: HTTP Batch Request Draft
- Re: HTTP Batch Request Draft
- HTTP Batch Request Draft
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal for i23: no-store invalidation
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal for i23: no-store invalidation
- Proposed Erratum for RFC 2817, was: Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
- Re: Proposal for i23: no-store invalidation
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal for i23: no-store invalidation
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Re: Proposal: 205 Bodies [#88]
- Proposal: 205 Bodies [#88]
- Re: Sending Referer [#144]
- Re: PROPOSAL: Content Sniffing impact on HTTPbis - #155
- Re: comments on draft-barth-mime-sniffing
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: comments on draft-barth-mime-sniffing
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- Re: httpbis-p6-cache-06 and no-store response directive
- Re: comments on draft-barth-mime-sniffing
- httpbis-p6-cache-06 and no-store response directive
- Re: draft-ietf-httpbis-p6-cache-06
Sunday, 7 June 2009
- Re: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- Re: Sending Referer [#144]
- Re: draft-ietf-httpbis-p6-cache-06
- Re: #172 (take over HTTP Upgrade Token Registry) – httpbis
- PROPOSAL: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
Saturday, 6 June 2009
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
Friday, 5 June 2009
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: #172 (take over HTTP Upgrade Token Registry) – httpbis
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: #172 (take over HTTP Upgrade Token Registry) – httpbis
- Re: Content Sniffing impact on HTTPbis - #155
- Re: comments on draft-barth-mime-sniffing
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: updating headers with 304 responses
- Re: Content Sniffing impact on HTTPbis - #155
- Re: allowing sniffed type list to be extensible? No.
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
- updating headers with 304 responses
- Re: Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
- Proposal: Is OPTIONS Safe? [#171]
- Re: Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
- Re: #172 (take over HTTP Upgrade Token Registry) – httpbis
- Re: Content Sniffing impact on HTTPbis - #155
Thursday, 4 June 2009
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
- Re: Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
- Re: Content Sniffing impact on HTTPbis - #155
- #172 (take over HTTP Upgrade Token Registry) – httpbis
- Re: i37: Vary and non-existant headers
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Is OPTIONS Safe? [#171]
- Re: Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
Wednesday, 3 June 2009
- Re: Vary: Cookie
- Re: Vary: Cookie
- Issue 170, was: IANA Registration Requirements for Status Codes and Method Names
- Re: IANA Registration Requirements for Status Codes and Method Names
- IANA Registration Requirements for Status Codes and Method Names
- Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs
- Re: draft-ietf-httpbis-p6-cache-06
- Re: Is OPTIONS Safe?
- Re: Vary: Cookie
- Re: Is OPTIONS Safe?
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Is OPTIONS Safe?
- Re: Content Sniffing impact on HTTPbis - #155
- Upcoming meetings (Stockholm and Hiroshima)
- Scope of redirection
- Is OPTIONS Safe?
- Vary: Cookie
- Re: draft-ietf-httpbis-p6-cache-06
Tuesday, 2 June 2009
- Re: CONNECT command with message body
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs
- Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs
- RE: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- Re: absolute URI in request to origin servers which are also proxies.
- Re: draft-ietf-httpbis-p6-cache-06
- Re: absolute URI in request to origin servers which are also proxies.
- Re: Content Sniffing impact on HTTPbis - #155
- Re: absolute URI in request to origin servers which are also proxies.
- Re: absolute URI in request to origin servers which are also proxies.
- Re: Content Sniffing impact on HTTPbis - #155
- Re: absolute URI in request to origin servers which are also proxies.
- absolute URI in request to origin servers which are also proxies.
- Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs
- Re: Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs
Monday, 1 June 2009
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Sending Referer [#144]
- Re: Sending Referer [#144]
- Re: Content Sniffing impact on HTTPbis - #155
- Issue 166: clarify term "User Agent" and resolve inconsistencies with W3C specs
- Re: Content Sniffing impact on HTTPbis - #155
- RE: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Sending Referer [#144]
- RE: Sending Referer [#144]
- Re: Sending Referer [#144]
- Re: Sending Referer [#144]
- Sending Referer [#144]
- Content Sniffing impact on HTTPbis - #155
- Re: comments on draft-barth-mime-sniffing
- Re: comments on draft-barth-mime-sniffing
Sunday, 31 May 2009
- Re: allowing sniffed type list to be extensible? No.
- Re: comments on draft-barth-mime-sniffing
- allowing sniffed type list to be extensible? No.
- RE: comments on draft-barth-mime-sniffing
Saturday, 30 May 2009
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
Friday, 29 May 2009
Thursday, 28 May 2009
Wednesday, 27 May 2009
- 408 Timeout details
- RE: draft-ietf-httpbis-p6-cache-06
- RE: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- RE: Cache-Control private="...", no-cache="..." (was RE: draft-ietf-httpbis-p6-cache-06)
- RE: draft-ietf-httpbis-p6-cache-06
- Re: Cache-Control private="...", no-cache="..." (was RE: draft-ietf-httpbis-p6-cache-06)
- Re: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- RE: draft-ietf-httpbis-p6-cache-06
- Re: draft-ietf-httpbis-p6-cache-06
- Re: relative weights of different Accept-* headers in content negotiation
- Cache-Control private="...", no-cache="..." (was RE: draft-ietf-httpbis-p6-cache-06)
- RE: draft-ietf-httpbis-p6-cache-06
- RE: relative weights of different Accept-* headers in content negotiation
- Re: relative weights of different Accept-* headers in content negotiation
- RE: relative weights of different Accept-* headers in content negotiation
- relative weights of different Accept-* headers in content negotiation
Tuesday, 26 May 2009
Monday, 25 May 2009
- Re: BNF for Cache-Control
- Re: BNF for Cache-Control
- OT: Re: Meaning of invalid but well-formed dates
- Re: BNF for Cache-Control
- Re: BNF for Cache-Control
- Re: BNF for Cache-Control
Sunday, 24 May 2009
Saturday, 23 May 2009
Friday, 22 May 2009
- Re: querystring part of cache key
- Re: querystring part of cache key
- Re: querystring part of cache key
- Re: querystring part of cache key
- Re: querystring part of cache key
- Re: querystring part of cache key
- querystring part of cache key
- Re: 12.2. Agent-driven negotiation
Thursday, 21 May 2009
- RE: Use of extension-header in entity-header
- Re: Use of extension-header in entity-header
- Re: Use of extension-header in entity-header
- Re: Use of extension-header in entity-header
- Re: 12.2. Agent-driven negotiation
- 12.2. Agent-driven negotiation
Wednesday, 20 May 2009
- RE: Use of extension-header in entity-header
- Re: Use of extension-header in entity-header
- RE: Use of extension-header in entity-header
- Use of extension-header in entity-header
Tuesday, 19 May 2009
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Issue 165, was: Issue 163, was: Meaning of invalid but well-formed dates
Monday, 18 May 2009
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: CONNECT command with message body
- TCP half-close behaviour
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- RE: Collected ABNF for HTTPbis
- Re: Collected ABNF for HTTPbis
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Collected ABNF for HTTPbis
- Re: CONNECT command with message body
- Re: Collected ABNF for HTTPbis
Sunday, 17 May 2009
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Collected ABNF for HTTPbis
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Collected ABNF for HTTPbis
- Re: Issue 163, was: Meaning of invalid but well-formed dates
Wednesday, 13 May 2009
Monday, 11 May 2009
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
Sunday, 10 May 2009
Saturday, 9 May 2009
Friday, 8 May 2009
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- RE: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 164, was: Statuscodes
- Issue 164, was: Statuscodes
- Statuscodes
- Re: i37: Vary and non-existant headers
- RE: i37: Vary and non-existant headers
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- RE: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- RE: i37: Vary and non-existant headers
- RE: i37: Vary and non-existant headers
Thursday, 7 May 2009
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- RE: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Issue 163, was: Meaning of invalid but well-formed dates
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
Wednesday, 6 May 2009
- Re: i37: Vary and non-existant headers
- RE: i37: Vary and non-existant headers
- RE: i37: Vary and non-existant headers
- RE: #110: how to determine what entity a response carries
- RE: NEW ISSUE: Drop Content-Location
- Re: #110: how to determine what entity a response carries
- Re: Issue 80 & 79, was: NEW ISSUE: Content-Location vs PUT/POST
- Re: #110: how to determine what entity a response carries
- Re: i37: Vary and non-existant headers
- Re: i37: Vary and non-existant headers
- Re: Issue 161, was: Base for first-byte-pos, last-byte-pos, suffix-length
- #110: how to determine what entity a response carries
- Re: Issue 161, was: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: i37: Vary and non-existant headers
- Re: Issue 161, was: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST
- Re: i37: Vary and non-existant headers
- Re: Issue 80, was: NEW ISSUE: Content-Location vs PUT/POST
- Re: i37: Vary and non-existant headers
- Re: NEW ISSUE: Drop Content-Location
Tuesday, 5 May 2009
- RE: nested comments [was: Ticket 162, was: Ambiguity in ABNF for comment]
- Re: nested comments [was: Ticket 162, was: Ambiguity in ABNF for comment]
- Re: nested comments [was: Ticket 162, was: Ambiguity in ABNF for comment]
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- Re: CONNECT command with message body
- CONNECT command with message body
- Re: iPhone streaming Internet-Draft posted
- Re: iPhone streaming Internet-Draft posted
Monday, 4 May 2009
- Re: Meaning of invalid but well-formed dates
- Re: Meaning of invalid but well-formed dates
- Re: nested comments [was: Ticket 162, was: Ambiguity in ABNF for comment]
- Re: nested comments [was: Ticket 162, was: Ambiguity in ABNF for comment]
- Re: nested comments [was: Ticket 162, was: Ambiguity in ABNF for comment]
- nested comments [was: Ticket 162, was: Ambiguity in ABNF for comment]
Sunday, 3 May 2009
- RE: Meaning of invalid but well-formed dates
- Re: Meaning of invalid but well-formed dates
- Re: Behaviour with malformed headers
- Re: Ticket 162, was: Ambiguity in ABNF for comment
- Meaning of invalid but well-formed dates
- Behaviour with malformed headers
- Re: Ticket 162, was: Ambiguity in ABNF for comment
- RE: Ticket 162, was: Ambiguity in ABNF for comment
Saturday, 2 May 2009
- Re: Ticket 162, was: Ambiguity in ABNF for comment
- Issue 161, was: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Ticket 162, was: Ambiguity in ABNF for comment
- RE: Ticket 162, was: Ambiguity in ABNF for comment
- RE: Base for first-byte-pos, last-byte-pos, suffix-length
- RE: Base for first-byte-pos, last-byte-pos, suffix-length
Friday, 1 May 2009
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- iPhone streaming Internet-Draft posted
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- RE: Base for first-byte-pos, last-byte-pos, suffix-length
- RE: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Ticket 162, was: Ambiguity in ABNF for comment
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
Thursday, 30 April 2009
Wednesday, 22 April 2009
Friday, 17 April 2009
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- URI/IRI revisions (was Re: Minutes from informal IETF/W3C meeting about HTML5 work)
- Re: Minutes from informal IETF/W3C meeting about HTML5 work
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: Review Comments for draft-nottingham-http-link-header-05
- Re: I-D Action:draft-nottingham-http-link-header-05.txt
- Re: I-D Action:draft-nottingham-http-link-header-05.txt
- Re: Fwd: I-D Action:draft-nottingham-http-link-header-05.txt
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Fwd: I-D Action:draft-nottingham-http-link-header-05.txt
- Closing #85: Custom ranges
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
Thursday, 16 April 2009
- Re: Link Relations and languages
- Re: Link Relations and languages
- RE: Base for first-byte-pos, last-byte-pos, suffix-length
- RE: [i161] Base for first-byte-pos, last-byte-pos, suffix-length
- Link Relations and languages
- RE: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: combining authenticated and anonymous access
- Re: Definition of 'resource' not consistent with RFC 3986
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: HTTP 301 responses for POST
- Re: [link draft] Changing the model for links
Wednesday, 15 April 2009
- Re: Retry-After header on 20X response -- HTTP/1.1 spec extension?
- Re: Empty host in 'http' scheme [#159]
Sunday, 12 April 2009
Saturday, 11 April 2009
Thursday, 9 April 2009
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- RE: PROPOSAL: content sniffing [#155]
- RE: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- Re: [link draft] Changing the model for links
- Re: PROPOSAL: content sniffing [#155]
- Re: [link draft] Changing the model for links
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
Wednesday, 8 April 2009
- Re: [link draft] Changing the model for links
- Re: PROPOSAL: content sniffing [#155]
- Re: [link draft] Changing the model for links
- Re: PROPOSAL: content sniffing [#155]
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- RE: Nit in section 2.1.1 of httpbis-p1
- Re: PROPOSAL: content sniffing [#155]
- Re: [link draft] Changing the model for links
- Re: NEW ISSUE: content sniffing
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- Re: PROPOSAL: content sniffing [#155]
- Re: Nit in section 2.1.1 of httpbis-p1
- RE: Nit in section 2.1.1 of httpbis-p1
- RE: NEW ISSUE: Drop Content-Location
- Re: PROPOSAL: content sniffing [#155]
- Re: PATCH draft
- Re: Users with different access rights in HTTP Authentication
- Re: [link draft] Changing the model for links
- Re: URI handling for Location
- Re: URI handling for Location
- Re: URI handling for Location
- Re: URI handling for Location
- Re: URI handling for Location
- Re: URI handling for Location
- Re: URI handling for Location
- Re: URI handling for Location
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- Re: URI handling for Location
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- Re: URI handling for Location
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- Re: [link draft] Changing the model for links
- RE: NEW ISSUE: content sniffing
- RE: NEW ISSUE: Drop Content-Location
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- Re: Users with different access rights in HTTP Authentication
- Re: PATCH draft
- Re: HTTP over SCTP without chunked encoding
- Re: HTTP pipelining - indirect security implications
- Re: PROPOSAL: content sniffing [#155]
- Re: PROPOSAL: content sniffing [#155]
- Re: Nit in section 2.1.1 of httpbis-p1
- Re: Keep-alive header in RFC2616 [#158]
- Re: PROPOSAL: content sniffing [#155]
- Re: Nit in section 2.1.1 of httpbis-p1
- Re: NEW ISSUE: isolate TCP-specific aspects of HTTP
- PROPOSAL: content sniffing [#155]
- Re: content sniffing (and HTTP profiling)
- Re: content sniffing (and HTTP profiling)
- Re: content sniffing (and HTTP profiling)
- Re: content sniffing (and HTTP profiling)
- Re: content sniffing (and HTTP profiling)
- RE: NEW ISSUE: Drop Content-Location
- RE: URI handling for Location
- Re: NEW ISSUE: content sniffing
Tuesday, 7 April 2009
- Re: content sniffing (and HTTP profiling)
- Re: content sniffing (and HTTP profiling)
- [link draft] Changing the model for links
- Re: NEW ISSUE: content sniffing
- Re: URI handling for Location
- Re: URI handling for Location
- Re: NEW ISSUE: Drop Content-Location
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: NEW ISSUE: Drop Content-Location
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Closing #90: multipart/byteranges
- Draft minutes for IETF74
- Closing #90: multipart/byteranges
- Re: URI handling for Location
- Re: NEW ISSUE: Drop Content-Location
- Closing #138: The role of Warning and Semantic Transparency in Caching
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: NEW ISSUE: Drop Content-Location
- Re: NEW ISSUE: Drop Content-Location
- Re: NEW ISSUE: Drop Content-Location
- RE: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
Monday, 6 April 2009
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Re: Questions about draft-abarth-mime-sniff-00
- Questions about draft-abarth-mime-sniff-00
- Re: p6-caching: commentary from -05 to -06
- Closing #83: OPTIONS * and proxies
- Closing #77: Line folding
- Closing #111: Use of TEXT
- Closing #74: Character Encodings in TEXT
- Closing #63: RFC2047 encoded words
- Closing #30: Header LWS
- Soliciting reviews for Cross-Origin Resource Sharing
Sunday, 5 April 2009
Saturday, 4 April 2009
- Re: NEW ISSUE: isolate TCP-specific aspects of HTTP
- Re: Pipelining in HTTP 1.1
- Re: Pipelining in HTTP 1.1
Friday, 3 April 2009
- Request for Review: Cross-Origin Resource Sharing
- Issue 153, was: case-sensitivity of weakness indicator
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
Thursday, 2 April 2009
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: case-sensitivity of weakness indicator
- HTTP pipelining - indirect security implications
- Re: NEW ISSUE: content sniffing
- HTTP over SCTP without chunked encoding
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
Wednesday, 1 April 2009
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- RE: Pipelining in HTTP 1.1
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- RE: Pipelining in HTTP 1.1
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: isolate TCP-specific aspects of HTTP
- Re: Pipelining in HTTP 1.1
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: Minutes from informal IETF/W3C meeting about HTML5 work
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing
- Re: NEW ISSUE: content sniffing