Wednesday, 30 December 2009
- Re: Proposal for i23: no-store invalidation [#117]
- Re: #197: Effect of CC directives on history lists
- Re: Proposal for i23: no-store invalidation [#117]
- Re: Proposal for i23: no-store invalidation [#117]
Tuesday, 29 December 2009
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: HTTP Mutual-auth proposal status / HTTP AUTH meet-up in Anaheim?
- Re: HTTP Mutual-auth proposal status / HTTP AUTH meet-up in Anaheim?
Monday, 28 December 2009
- Re: Last call for comments on draft-reschke-rfc2231-in-http-07
- Last call for comments on draft-reschke-rfc2231-in-http-07
Thursday, 24 December 2009
- Re: HTTP Mutual-auth proposal status / HTTP AUTH meet-up in Anaheim?
- HTTP Mutual-auth proposal status / HTTP AUTH meet-up in Anaheim?
Wednesday, 23 December 2009
Monday, 21 December 2009
- suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- Re: TAG requests addition to section 3.2.1 of Part 3
- Re: TAG requests addition to section 3.2.1 of Part 3
Friday, 18 December 2009
- TAG requests addition to section 3.2.1 of Part 3
- Re: Does "obs-" prefix in draft-ietf-httpbis-p* ABNF stand for "obsolete" ?
- Does "obs-" prefix in draft-ietf-httpbis-p* ABNF stand for "obsolete" ?
Tuesday, 15 December 2009
Saturday, 12 December 2009
- Re: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- RE: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- RE: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- RE: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
Thursday, 10 December 2009
- Re: Last Call: draft-bryan-http-digest-algorithm-values-update (Additional Hash Algorithms for HTTP Instance Digests) to Informational RFC
- Re: Last Call: draft-bryan-http-digest-algorithm-values-update (Additional Hash Algorithms for HTTP Instance Digests) to Informational RFC
- Re: Protocol Action: 'PATCH Method for HTTP' to Proposed Standard
- Re: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- Re: Last Call: draft-bryan-http-digest-algorithm-values-update (Additional Hash Algorithms for HTTP Instance Digests) to Informational RFC
Wednesday, 9 December 2009
- RE: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- Re: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- RE: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- Re: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- RE: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
Tuesday, 8 December 2009
Monday, 7 December 2009
- RE: Authentication realm
- Re: Authentication realm
- Re: Last Call: draft-bryan-http-digest-algorithm-values-update (Additional Hash Algorithms for HTTP Instance Digests) to Informational RFC
- RE: Authentication realm
- Re: Authentication realm
Sunday, 6 December 2009
- Authentication realm
- Re: Interpretation of response body in case of PUT and 200 Ok
- Interpretation of response body in case of PUT and 200 Ok
Saturday, 5 December 2009
- RE: Last Call: draft-bryan-http-digest-algorithm-values-update (Additional Hash Algorithms for HTTP Instance Digests) to Informational RFC
- Re: Last Call: draft-bryan-http-digest-algorithm-values-update (Additional Hash Algorithms for HTTP Instance Digests) to Informational RFC
Friday, 4 December 2009
- Re: Persistent connection timeout
- RE: Backwards definition of authentication header
- RE: Last Call: draft-bryan-http-digest-algorithm-values-update (Additional Hash Algorithms for HTTP Instance Digests) to Informational RFC
- Re: Backwards definition of authentication header
- RE: Backwards definition of authentication header
- Authentication-Info Header
- Re: for GET, does the request-target identify information?
- RE: Backwards definition of authentication header
- RE: Backwards definition of authentication header
- RE: Multiple challenges in a single WWW-Authenticate header field
- Re: RFC2616 vs draft-ietf-httpbis-p7-auth
- Re: Backwards definition of authentication header
- Persistent connection timeout
- Re: Backwards definition of authentication header
- Re: Multiple challenges in a single WWW-Authenticate header field
- Re: [OAUTH-WG] RFC2616 vs draft-ietf-httpbis-p7-auth
- RE: Multiple challenges in a single WWW-Authenticate header field
- Re: Multiple challenges in a single WWW-Authenticate header field
- Backwards definition of authentication header
- Re: Multiple challenges in a single WWW-Authenticate header field
- Re: Multiple challenges in a single WWW-Authenticate header field
- Multiple challenges in a single WWW-Authenticate header field
- RFC2616 vs draft-ietf-httpbis-p7-auth
Wednesday, 2 December 2009
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: DNS rebinding not mentioned in "HTTP/1.1, part 1"
- Re: DNS rebinding not mentioned in "HTTP/1.1, part 1"
Tuesday, 1 December 2009
- Re: fyi: W3C web security mailing list (announcement) (was: HTTPbis and the Same Origin Policy)
- fyi: W3C web security mailing list (announcement) (was: HTTPbis and the Same Origin Policy)
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- W3C web security mailing list (Re: HTTPbis and the Same Origin Policy)
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: #131: Connection limits (proposal)
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
Monday, 30 November 2009
- Re: HTTPbis and the Same Origin Policy
- RE: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: #131: Connection limits (proposal)
- Closing #145 - empty authority in URL
Thursday, 26 November 2009
- Content-Location and etag, was: I-D Action:draft-dusseault-http-patch-16.txt
- Re: Media type for 300/406 responses?
- Re: Media type for 300/406 responses?
- RE: I-D Action:draft-dusseault-http-patch-16.txt
- Media type for 300/406 responses?
- Re: I-D Action:draft-dusseault-http-patch-16.txt
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: FYI Cache-control deployment
Wednesday, 25 November 2009
- Re: HTTPbis and the Same Origin Policy
- Re: FYI Cache-control deployment
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: FYI Cache-control deployment
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- FYI Cache-control deployment
- Last Call: draft-roach-sip-http-subscribe-03
- Re: issue 85 - range unit extensions
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Request for Comments: XMLHttpRequest Last Call Working Draft; deadline 15 December 2009
- Re: HTTPbis and the Same Origin Policy
- Re: HTTPbis and the Same Origin Policy
- Re: issue 85 - range unit extensions
- Re: issue 85 - range unit extensions
- Re: HTTPbis and the Same Origin Policy
- Re: issue 85 - range unit extensions
- Re: HTTPbis and the Same Origin Policy
- HTTPbis and the Same Origin Policy
- DNS rebinding not mentioned in "HTTP/1.1, part 1"
- DNS rebinding not mentioned in "HTTP/1.1, part 1"
- Re: CSRF and clickjacking not mentioned in "HTTP/1.1, part 7: Authentication"
- CSRF and clickjacking not mentioned in "HTTP/1.1, part 7: Authentication"
Tuesday, 24 November 2009
Monday, 23 November 2009
Friday, 20 November 2009
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: What are "appropriate Cache-Control or Expires header fields"
Wednesday, 18 November 2009
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
Tuesday, 17 November 2009
Wednesday, 18 November 2009
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
Tuesday, 17 November 2009
- Re: FYI: Mozilla's Resource Packages
- Re: FYI: Mozilla's Resource Packages
- FYI: Mozilla's Resource Packages
Monday, 16 November 2009
- Re: "start", "first" and "last" in link relations draft, RDFa and (X)HTML
- "start", "first" and "last" in link relations draft, RDFa and (X)HTML
Friday, 13 November 2009
Thursday, 12 November 2009
Friday, 13 November 2009
- Re: Duplicate Referrer Header - HTTP.sys barfs - Stack Overflow
- Re: Authorization with WWW-Authenticate (bis)
- Re: Input on request for link relation
Thursday, 12 November 2009
- Re: Input on request for link relation
- Re: Duplicate Referrer Header - HTTP.sys barfs - Stack Overflow
- Re: Authorization with WWW-Authenticate (bis)
- Fwd: Heads-up: Last Call Working Draft of XHR (1) to be published on Nov 24
- Re: Input on request for link relation
- Re: Input on request for link relation
Wednesday, 11 November 2009
- Re: Authorization with WWW-Authenticate (bis)
- Re: Authorization with WWW-Authenticate (bis)
- Re: Authorization with WWW-Authenticate (bis)
- Re: Multi-server HTTP
- Re: Authorization with WWW-Authenticate (bis)
- Re: Input on request for link relation [ w/ proposed modifications to link draft ]
- Re: Authorization with WWW-Authenticate (bis)
- RE: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- RE: What are "appropriate Cache-Control or Expires header fields"
- Re: Duplicate Referrer Header - HTTP.sys barfs - Stack Overflow
- Duplicate Referrer Header - HTTP.sys barfs - Stack Overflow
Tuesday, 10 November 2009
- Re: Multi-server HTTP
- Re: Multi-server HTTP
- Re: [Ltru] Issue 181, was: Issue 113 (language tag matching (Accept-Language) vs RFC4647), was: Proposed resolution for Issue 13 (language tags)
Monday, 9 November 2009
Saturday, 7 November 2009
Wednesday, 4 November 2009
Tuesday, 3 November 2009
- Re: What are "appropriate Cache-Control or Expires header fields"
- [Reminder] Review of Guidelines for Web Content Transformation Guidelines
Thursday, 29 October 2009
Wednesday, 28 October 2009
- Re: wrt HTTP Origin header serialization (was Re: The HTTP Sec-From Header (draft-abarth-origin))
- Re: The HTTP Sec-From Header (draft-abarth-origin)
- Re: The HTTP Sec-From Header (draft-abarth-origin)
- Re: wrt HTTP Origin header serialization (was Re: The HTTP Sec-From Header (draft-abarth-origin))
- Re: The HTTP Sec-From Header (draft-abarth-origin)
Tuesday, 27 October 2009
- wrt HTTP Origin header serialization (was Re: The HTTP Sec-From Header (draft-abarth-origin))
- Re: The HTTP Sec-From Header (draft-abarth-origin)
- Re: Instance Digests in HTTP (RFC3230)
- HTTPbis -08 drafts published
- Re: Last Call: draft-dusseault-http-patch (PATCH Method for HTTP) to Proposed Standard
Monday, 26 October 2009
- Fwd: I-D Action:draft-wood-dtnrg-http-dtn-delivery-04.txt
- I-D Action:draft-ietf-httpbis-p7-auth-08.txt
- I-D Action:draft-ietf-httpbis-p6-cache-08.txt
- I-D Action:draft-ietf-httpbis-p5-range-08.txt
- I-D Action:draft-ietf-httpbis-p4-conditional-08.txt
- I-D Action:draft-ietf-httpbis-p3-payload-08.txt
- I-D Action:draft-ietf-httpbis-p2-semantics-08.txt
- I-D Action:draft-ietf-httpbis-p1-messaging-08.txt
Sunday, 25 October 2009
Saturday, 24 October 2009
Friday, 23 October 2009
- Re: Authorization with WWW-Authenticate (bis)
- Nov 2nd - Social Web Camp in Santa Clara
- Authorization with WWW-Authenticate (bis)
Thursday, 22 October 2009
- Re: What are "appropriate Cache-Control or Expires header fields"
- RE: What are "appropriate Cache-Control or Expires header fields"
- Re: What are "appropriate Cache-Control or Expires header fields"
- RE: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- RE: What are "appropriate Cache-Control or Expires header fields"
- Re: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: [OT] Re: #131: Connection limits (proposal)
Wednesday, 21 October 2009
Tuesday, 20 October 2009
- Re: [OT] Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- RE: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- Re: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- RE: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- Re: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
Monday, 19 October 2009
- Re: #131: Connection limits (proposal)
- Re: [OT] Re: #131: Connection limits (proposal)
- Re: [OT] Re: #131: Connection limits (proposal)
- Re: [OT] Re: #131: Connection limits (proposal)
- Re: [OT] Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- Re: Multi-server HTTP
- RE: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- Re: [OT] Re: #131: Connection limits (proposal)
- Re: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- [OT] Re: #131: Connection limits (proposal)
- Re: weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- Re: #131: Connection limits (proposal)
- #131: Connection limits (proposal)
Friday, 16 October 2009
- Issue 123, was: I-D Action:draft-reschke-rfc2183-in-http-00.txt
- weak etags vs PATCH, was: Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
Thursday, 15 October 2009
- Fwd: New Version Notification - draft-dusseault-http-patch-15.txt
- RE: Which status codes are cacheable?
- Re: Instance Digests in HTTP (RFC3230)
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: #178: Content-MD5 and partial responses
- Re: Issue 188, was: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)
- FYI: draft-wing-http-new-tech
Wednesday, 14 October 2009
- RE: What are "appropriate Cache-Control or Expires header fields"
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: i37: Vary and non-existant headers
- #29: correcting corrected_initial_age
- Re: NEW ISSUE: Drop Content-Location [#154]
- RE: What are "appropriate Cache-Control or Expires header fields"
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: What are "appropriate Cache-Control or Expires header fields"
- RE: What are "appropriate Cache-Control or Expires header fields"
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: Which status codes are cacheable?
- Re: #169: private and no-cache CC directives w/ header args
- Re: #173: CR and LF in chunk extension values
- Re: NEW ISSUE: Drop Content-Location [#154]
Tuesday, 13 October 2009
Monday, 12 October 2009
Sunday, 11 October 2009
Friday, 9 October 2009
- Re: Multi-server HTTP
- Re: draft-bryan-http-digest-algorithm-values-update-00 open issues
- Fwd: I-D Action:draft-wing-behave-http-ip-address-literals-00.txt
Thursday, 8 October 2009
- Re: header parsing, trailing OWS
- Issue 196, was: #110: how to determine what entity a response carries
- Re: header parsing, trailing OWS
- Re: Issue 43 (combining fragments)
- RE: Issue 43 (combining fragments)
- Re: Issue 43 (combining fragments)
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: #178: Content-MD5 and partial responses
- RE: Clarifying Content-Location (Issue 136)
- Re: #178: Content-MD5 and partial responses
- Re: #197: Effect of CC directives on history lists
- RE: #197: Effect of CC directives on history lists
- RE: #178: Content-MD5 and partial responses
- RE: Issue 43 (combining fragments)
- #178: Content-MD5 and partial responses
- Re: Issue 43 (combining fragments)
- Re: #197: Effect of CC directives on history lists
- Re: #184: HTTP/0.9
Wednesday, 7 October 2009
- Re: header parsing, trailing OWS
- Re: header parsing, trailing OWS
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: header parsing, trailing OWS
- Re: Issue 43 (combining fragments)
- RE: Issue 43 (combining fragments)
- Re: header parsing, trailing OWS
- Re: Issue 43 (combining fragments)
- Re: Issue 43 (combining fragments)
- Re: Issue 43 (combining fragments)
- Re: Proposal: Is OPTIONS Safe? [#171]
- Re: header parsing, trailing OWS
- Re: #173: CR and LF in chunk extension values
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: Clarifying Content-Location (Issue 136)
Tuesday, 6 October 2009
Wednesday, 7 October 2009
Tuesday, 6 October 2009
- Re: Instance Digests in HTTP (RFC3230)
- Re: Clarifying Content-Location (Issue 136)
- Re: Instance Digests in HTTP (RFC3230)
- Re: Instance Digests in HTTP (RFC3230)
- Review of Guidelines for Web Content Transformation Guidelines
- Re: ambiguous ABNF in RFC 2231 (and friends)
- RE: Clarifying Content-Location (Issue 136)
- Re: Clarifying Content-Location (Issue 136)
- Re: #167: Content-Location on 304 responses
- Re: [#54] 13.1.2's Definition of 1xx Warn-Codes
- Re: Clarifying Content-Location (Issue 136)
- Re: Clarifying Content-Location (Issue 136)
- Re: Clarifying Content-Location (Issue 136)
- RE: Clarifying Content-Location (Issue 136)
- Re: Clarifying Content-Location (Issue 136)
- RE: Clarifying Content-Location (Issue 136)
- RE: Clarifying Content-Location (Issue 136)
- Re: i37: Vary and non-existant headers
- Re: #173: CR and LF in chunk extension values
- Re: [httpbis] #81: Content Negotiation for media types
- Re: Empty host in 'http' scheme [#159]
- Re: NEW ISSUE: Drop Content-Location [#154]
- Re: Issue 194: restricting allowed characters in quoted-pair
- Re: Clarifying Content-Location (Issue 136)
- Re: Clarifying Content-Location (Issue 136)
- Re: #110: how to determine what entity a response carries
- Re: ambiguous ABNF in RFC 2231 (and friends)
Monday, 5 October 2009
Sunday, 4 October 2009
- Re: I-D Action:draft-reschke-rfc2231-in-http-04.txt
- Re: Instance Digests in HTTP (RFC3230)
- Re: Instance Digests in HTTP (RFC3230)
Saturday, 3 October 2009
- Re: I-D Action:draft-reschke-rfc2231-in-http-03.txt
- RE: realms
- Re: Multi-server HTTP
- Re: Multi-server HTTP
Friday, 2 October 2009
- Re: Multi-server HTTP
- Re: CSP spec vs listed-type headers
- CSP spec vs listed-type headers
- RE: Multi-server HTTP