Re: I-D Action:draft-reschke-rfc2231-in-http-11.txt
IETF77 meeting minutes
Re: 100 Continue and Expects
proposal for issue #175 range flooding
Issue 39: proposed example for varying the etag based on conneg
proposal for issue #178
httpbis and deflate compression...
Comment on draft-reschke-rfc2231-in-http-10 section 4.3
Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
Re: RFC 5789 on PATCH Method for HTTP
HTTPbis Working Group meeting next Monday in Anaheim, CA
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?
3 short questions, Entity Tag & Content Location
- Re: 3 short questions, Entity Tag & Content Location
- Re: 3 short questions, Entity Tag & Content Location
W3C Account and HTMLWG Participation "Unlinked"
300 Multiple Choices and safe methods
I-D ACTION:draft-ietf-httpbis-security-properties-05.txt
Re: [Fwd: Request for feedback on HTTP Location header syntax + semantics, Re: Issues 43 and 185, was: Issue 43 (combining fragments)]
I-D ACTION:draft-ietf-httpbis-security-properties-04.txt
- Re: I-D ACTION:draft-ietf-httpbis-security-properties-04.txt
- Re: I-D ACTION:draft-ietf-httpbis-security-properties-04.txt
no-cache response directive
Issues addressed in -09 drafts
#204 (editorial): Clock requirement for caches
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
New version of Cache Context draft
Amazon.com - Your Cancellation (495-265546-13651)
HTTPbis Range header
DRAFT Anaheim agenda
Re: #29: correcting corrected_initial_age
- Re: #29: correcting corrected_initial_age
Re: Issue 43 (combining fragments)
- Issues 43 and 185, was: Issue 43 (combining fragments)
- 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)
- 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)
- 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)
- 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)
- 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: 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)
- 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)
#147: header-specific canonicalisation
- Re: #147: header-specific canonicalisation
- Re: #147: header-specific canonicalisation
Re: What are "appropriate Cache-Control or Expires header fields"
Fwd: New Version Notification - draft-nottingham-http-link-header-08.txt
- 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)
one time passwords from private keys
Cache behavior for authenticated contents
[410 Gone] HTTP/1.1, part 2: Message Semantics
FYI: Anaheim IETF meeting
FYI: IETF LC for draft-reschke-rfc2231-in-http
Expect: 100-continue and proxies
p1-messaging proofreading
User interface requirements for redirecting to unsafe methods
- Re: User interface requirements for redirecting to unsafe methods
Review of third Last Call of Guidelines for Web Content Transformation Proxies
The meaning of rev
Security considerations for DNS rebinding
- issue 202, was: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
- Re: Security considerations for DNS rebinding
FWD: I-D Action:draft-reschke-rfc2231-in-http-09.txt
p2-semantics proofreading
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
Clarification of http-409
p3-payload proofreading
FYI: Google blog on Unicode
p4-conditional proofreading
p5-range typo
p7-auth typo
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
Why do caching heuristics exclude 303?
issue 201, was: header parsing, trailing OWS
Re: Last Call: draft-nottingham-http-link-header (Web Linking) to Proposed Standard
FYI: review of draft-abarth-mime-sniff-03
Re: Authentication-Info Header
- Re: [OAUTH-WG] Authentication-Info Header
- Re: Authentication-Info Header
- Re: [OAUTH-WG] Authentication-Info Header
Re: [Fwd: WWW-Authenticate challenge for client-certificates]
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: New Version Notification - draft-nottingham-http-link-header-07.txt
- Re: Fwd: New Version Notification - draft-nottingham-http-link-header-07.txt
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- Re: anchor parameter - LC comment on draft-nottingham-http-link-header-07.txt
- 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
- Re: rev parameter - LC comment on draft-nottingham-http-link-header-07.txt
Meeting plans re. Anaheim?
Long-polling to monitor resources
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: 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
(Updating "content negotiation" language, issue 81), and TCN RFC 2295 to Proposed?
Content Negotiation again
Re: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
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