Wednesday, 31 March 2010
Tuesday, 30 March 2010
Monday, 29 March 2010
Tuesday, 30 March 2010
Monday, 29 March 2010
- Re: 100 Continue and Expects
- Re: 100 Continue and Expects
- Re: 100 Continue and Expects
- Re: Comment on draft-reschke-rfc2231-in-http-10 section 4.3
- Re: FYI: IETF LC for draft-reschke-rfc2231-in-http
- Re: #73: httpbis and deflate compression...
- Re: #73: httpbis and deflate compression...
Sunday, 28 March 2010
- Re: 100 Continue and Expects
- Re: 100 Continue and Expects
- Re: 100 Continue and Expects
- Re: #73: httpbis and deflate compression...
- Re: 100 Continue and Expects
- Re: 100 Continue and Expects
Saturday, 27 March 2010
Friday, 26 March 2010
- #73: httpbis and deflate compression...
- Re: httpbis and deflate compression...
- RE: httpbis and deflate compression...
- Re: httpbis and deflate compression...
Thursday, 25 March 2010
- Re: Issue 39: proposed example for varying the etag based on conneg
- proposal for issue #175 range flooding
- Issue 39: proposed example for varying the etag based on conneg
- proposal for issue #178
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
Tuesday, 23 March 2010
- Re: httpbis and deflate compression...
- Re: httpbis and deflate compression...
- httpbis and deflate compression...
Monday, 22 March 2010
- Comment on draft-reschke-rfc2231-in-http-10 section 4.3
- Re: DRAFT Anaheim agenda
- Re: #29: correcting corrected_initial_age
Sunday, 21 March 2010
Friday, 19 March 2010
Thursday, 18 March 2010
Wednesday, 17 March 2010
Monday, 15 March 2010
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
Sunday, 14 March 2010
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 3 short questions, Entity Tag & Content Location
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 3 short questions, Entity Tag & Content Location
- Re: 3 short questions, Entity Tag & Content Location
- Re: 3 short questions, Entity Tag & Content Location
- Re: 204 No Content for a resource which is known but has no representation yet?
- Re: 204 No Content for a resource which is known but has no representation yet?
- 204 No Content for a resource which is known but has no representation yet?
Saturday, 13 March 2010
Friday, 12 March 2010
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- 3 short questions, Entity Tag & Content Location
- W3C Account and HTMLWG Participation "Unlinked"
Thursday, 11 March 2010
- Re: #29: correcting corrected_initial_age
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
Wednesday, 10 March 2010
Thursday, 11 March 2010
Wednesday, 10 March 2010
- I-D ACTION:draft-ietf-httpbis-security-properties-05.txt
- Re: I-D ACTION:draft-ietf-httpbis-security-properties-04.txt
- Re: I-D ACTION:draft-ietf-httpbis-security-properties-04.txt
- Re: [Fwd: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)]
- warning: redirect test cases broken, was: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: I-D ACTION:draft-ietf-httpbis-security-properties-04.txt
- I-D ACTION:draft-ietf-httpbis-security-properties-04.txt
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: #29: correcting corrected_initial_age
- Re: no-cache response directive
- Re: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: #29: correcting corrected_initial_age
- no-cache response directive
- Issues addressed in -09 drafts
Tuesday, 9 March 2010
- #204 (editorial): Clock requirement for caches
- Re: #29: correcting corrected_initial_age
- Issues 43 and 185, was: Issue 43 (combining fragments)
- Re: #29: correcting corrected_initial_age
- Re: rel=meta and the Link Relation Type registry (was Re: New Version Notification - draft-nottingham-http-link-header-08.txt)
- Re: rel=meta and the Link Relation Type registry (was Re: New Version Notification - draft-nottingham-http-link-header-08.txt)
- Re: rel=meta and the Link Relation Type registry (was Re: New Version Notification - draft-nottingham-http-link-header-08.txt)
- Re: rel=meta and the Link Relation Type registry (was Re: New Version Notification - draft-nottingham-http-link-header-08.txt)
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: #29: correcting corrected_initial_age
- Re: HTTPbis Range header
- Re: #29: correcting corrected_initial_age
Monday, 8 March 2010
- Re: #29: correcting corrected_initial_age
- Re: #29: correcting corrected_initial_age
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: #29: correcting corrected_initial_age
- Re: #29: correcting corrected_initial_age
- I-D Action:draft-ietf-httpbis-p7-auth-09.txt
- I-D Action:draft-ietf-httpbis-method-registrations-03.txt
- I-D Action:draft-ietf-httpbis-p5-range-09.txt
- I-D Action:draft-ietf-httpbis-p4-conditional-09.txt
- I-D Action:draft-ietf-httpbis-p3-payload-09.txt
- I-D Action:draft-ietf-httpbis-p6-cache-09.txt
- I-D Action:draft-ietf-httpbis-p2-semantics-09.txt
- I-D Action:draft-ietf-httpbis-p1-messaging-09.txt
Sunday, 7 March 2010
Saturday, 6 March 2010
Friday, 5 March 2010
Thursday, 4 March 2010
- Re: #147: header-specific canonicalisation
- Re: #147: header-specific canonicalisation
- rel=meta and the Link Relation Type registry (was Re: New Version Notification - draft-nottingham-http-link-header-08.txt)
- Re: #147: header-specific canonicalisation
- Re: #147: header-specific canonicalisation
- Re: #147: header-specific canonicalisation
- DRAFT Anaheim agenda
- Re: #29: correcting corrected_initial_age
- Re: #147: header-specific canonicalisation
Wednesday, 3 March 2010
- Re: #147: header-specific canonicalisation
- Re: Issue 43 (combining fragments)
- Re: #147: header-specific canonicalisation
- Re: #147: header-specific canonicalisation
- Re: #197: Effect of CC directives on history lists
- #147: header-specific canonicalisation
- Re: What are "appropriate Cache-Control or Expires header fields"
- Re: #197: Effect of CC directives on history lists
Tuesday, 2 March 2010
Monday, 1 March 2010
Sunday, 28 February 2010
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- one time passwords from private keys
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
Friday, 26 February 2010
- Cache behavior for authenticated contents
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
Thursday, 25 February 2010
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: [410 Gone] HTTP/1.1, part 2: Message Semantics
- [410 Gone] HTTP/1.1, part 2: Message Semantics
Tuesday, 23 February 2010
Monday, 22 February 2010
- Re: Expect: 100-continue and proxies
- FYI: IETF LC for draft-reschke-rfc2231-in-http
- Re: Expect: 100-continue and proxies
Sunday, 21 February 2010
Friday, 19 February 2010
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
Wednesday, 17 February 2010
Tuesday, 16 February 2010
Sunday, 14 February 2010
- Re: User interface requirements for redirecting to unsafe methods
- Re: User interface requirements for redirecting to unsafe methods
- Re: User interface requirements for redirecting to unsafe methods
Friday, 12 February 2010
- Re: Issue 10, was: User interface requirements for redirecting to unsafe methods
- Issue 10, was: User interface requirements for redirecting to unsafe methods
- Re: User interface requirements for redirecting to unsafe methods
- Re: User interface requirements for redirecting to unsafe methods
- User interface requirements for redirecting to unsafe methods
Thursday, 11 February 2010
Wednesday, 10 February 2010
- The meaning of rev
- Re: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
Tuesday, 9 February 2010
- Re: issue 202, was: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- RE: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- issue 202, was: Security considerations for DNS rebinding
- Security considerations for DNS rebinding
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
Monday, 8 February 2010
- Re: p2-semantics proofreading
- Re: p3-payload proofreading
- FWD: I-D Action:draft-reschke-rfc2231-in-http-09.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
Sunday, 7 February 2010
Friday, 5 February 2010
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- Re: allowable characters in token as used in parameter ABNF
- allowable characters in token as used in parameter ABNF
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- rfc2231-in-http: token characters, was: FYI: I-D Action:draft-reschke-rfc2231-in-http-08.txt
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
Thursday, 4 February 2010
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: editorial LC comments on draft-nottingham-http-link-header-07.txt
Wednesday, 3 February 2010
Tuesday, 2 February 2010
- Re: p3-payload proofreading
- Re: p3-payload proofreading
- Re: p3-payload proofreading
- Re: p3-payload proofreading
- p3-payload proofreading
Monday, 1 February 2010
- Re: p4-conditional proofreading
- Re: p4-conditional proofreading
- Re: p4-conditional proofreading
- Re: FYI: Google blog on Unicode
- FYI: Google blog on Unicode
Sunday, 31 January 2010
- Re: Past Proposals for HTTP Auth Logout
- Re: p4-conditional proofreading
- Re: Past Proposals for HTTP Auth Logout
- Re: p4-conditional proofreading
- Re: Past Proposals for HTTP Auth Logout
Saturday, 30 January 2010
Friday, 29 January 2010
- p4-conditional proofreading
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: Past Proposals for HTTP Auth Logout
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: exposing sensitive information in URIs - LC comments on draft-nottingham-http-link-header-07.txt
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: Past Proposals for HTTP Auth Logout
Thursday, 28 January 2010
- Re: p5-range typo
- p5-range typo
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Content Sniffing impact on HTTPbis - #155
- Re: Content Sniffing impact on HTTPbis - #155
Wednesday, 27 January 2010
Tuesday, 26 January 2010
- 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: Past Proposals for HTTP Auth Logout
Friday, 22 January 2010
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Why do caching heuristics exclude 303?
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: editorial LC comments on draft-nottingham-http-link-header-07.txt
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
Thursday, 21 January 2010
- Re: [hybi] Long-polling to monitor resources
- Re: FYI: review of draft-abarth-mime-sniff-03
- Re: issue 201, was: header parsing, trailing OWS
- issue 201, was: header parsing, trailing OWS
- Re: parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt
- Re: parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt
- exposing sensitive information in URIs - LC comments on draft-nottingham-http-link-header-07.txt
- editorial LC comments on draft-nottingham-http-link-header-07.txt
- parameter quoting - LC comment on draft-nottingham-http-link-header-07.txt
- rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
- anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
- Re: [OAUTH-WG] Authentication-Info Header
- Re: Authentication-Info Header
- Re: FYI: review of draft-abarth-mime-sniff-03
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: FYI: review of draft-abarth-mime-sniff-03
Wednesday, 20 January 2010
- FYI: review of draft-abarth-mime-sniff-03
- Re: #197: Effect of CC directives on history lists
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: [OAUTH-WG] Authentication-Info Header
- Re: Authentication-Info Header
- Re: [Fwd: WWW-Authenticate challenge for client-certificates]
- Re: Fwd: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: WWW-Authenticate challenge for client-certificates
Tuesday, 19 January 2010
- Re: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: #197: Effect of CC directives on history lists
- WWW-Authenticate challenge for client-certificates
- FYI: I-D Action:draft-reschke-rfc2231-in-http-08.txt
- Fwd: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: #197: Effect of CC directives on history lists
- Re: Meeting plans re. Anaheim
Sunday, 17 January 2010
Friday, 15 January 2010
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: Content Negotiation again
Thursday, 14 January 2010
Wednesday, 13 January 2010
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: Past Proposals for HTTP Auth Logout
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: Content Negotiation again
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- RE: Content Negotiation again
- Re: Past Proposals for HTTP Auth Logout
Tuesday, 12 January 2010
- Re: Content Negotiation again
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
Saturday, 9 January 2010
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- (Updating "content negotiation" language, issue 81), and TCN RFC 2295 to Proposed?
- Re: Past Proposals for HTTP Auth Logout
- Content Negotiation again
- Re: Past Proposals for HTTP Auth Logout
Friday, 8 January 2010
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
Thursday, 7 January 2010
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Re: Past Proposals for HTTP Auth Logout
- Past Proposals for HTTP Auth Logout