Status code for enforcing conditional requests
Pipelining clarification
HTTP 402 Payment Required
Please document that successful GET constitutes a retrieval
- Re: Please document that successful GET constitutes a retrieval
- Re: Please document that successful GET constitutes a retrieval
OT re HTTP auth disassocation of credentials
Issues with header combination text from draft -16
Re: I-D Action: draft-reschke-rfc5987bis-01.txt
Expect header 'understand' vs 'meet'
- Re: Expect header 'understand' vs 'meet'
OWS, line-folding and quoted-string
Re: SHOULD-level requirements in p6-caching
Issues addressed in the -16 drafts
#306: does etag value really use quoted-string
- Re: #306: does etag value really use quoted-string
- Re: #306: does etag value really use quoted-string
- Re: #306: does etag value really use quoted-string
idea for a helpful short discussion to add into section 5 (ranges)
- Re: idea for a helpful short discussion to add into section 5 (ranges)
- Re: idea for a helpful short discussion to add into section 5 (ranges)
an edit for easy reading on 5.4.1 "byte ranges"
IW10 Considered Harmful
The use of HTTP 501
2.2 Method Registry - Not Found
OWS in httpbis-p1-messaging
DELETE and 410 Gone
- Re: DELETE and 410 Gone
- Re: DELETE and 410 Gone
- Re: DELETE and 410 Gone
- Re: DELETE and 410 Gone
- Re: DELETE and 410 Gone
httpbis -16 drafts
I-D ACTION:draft-ietf-httpbis-p7-auth-16.txt
I-D ACTION:draft-ietf-httpbis-p4-conditional-16.txt
I-D ACTION:draft-ietf-httpbis-p5-range-16.txt
I-D ACTION:draft-ietf-httpbis-p6-cache-16.txt
I-D ACTION:draft-ietf-httpbis-p2-semantics-16.txt
I-D ACTION:draft-ietf-httpbis-p3-payload-16.txt
I-D ACTION:draft-ietf-httpbis-p1-messaging-16.txt
I-D Action: draft-ietf-httpbis-authscheme-registrations-02.txt
Ambiguities in header-field rules (p1-messaging)
- Re: Ambiguities in header-field rules (p1-messaging)
part 1 section 4.1.2 - authority form
Fwd: I-D Action: draft-nottingham-http-new-status-00.txt
Pipeline hinting revisited
- Re: Pipeline hinting revisited
Filling out 202 Accepted
WWW-Authenticate ABNF is ambiguous
#287: LWS in auth-param ABNF
proposed part 1 section 6.3
motivate 6.3 product tokens
Re: Fwd: IESG Statement on Designating RFCs as Historic [#254]
Issue 274 (again)
Re: #178: Content-MD5 and partial responses
#308: need to reserve "negotiate" as auth scheme name
- Re: #308: need to reserve "negotiate" as auth scheme name
- Re: #308: need to reserve "negotiate" as auth scheme name
if-range requests and compressed response
- Re: if-range requests and compressed response
- Re: if-range requests and compressed response
- Re: if-range requests and compressed response
#195, was: ABNF for Authorization header not quite right
- RE: #195, was: ABNF for Authorization header not quite right
- RE: #195, was: ABNF for Authorization header not quite right
- Re: #195, was: ABNF for Authorization header not quite right
#309: credentials ABNF missing SP (still using implied LWS?)
#270: \-escaping in quoted strings
line folding - ABNF vs prose
#306: does etag value really use quoted-string
- Re: #306: does etag value really use quoted-string
- Re: #306: does etag value really use quoted-string
Quebec Minutes
#257: Considerations for new authentications schemes
Updated agenda
Tracking through cache abuse
#177: Realm required on challenges
- Re: #177: Realm required on challenges
Re: #186: Document HTTP's error-handling philosophy
#78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- RE: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
- Re: #78: Relationship between 401, Authorization and WWW-Authenticate
#290: Motivate one-year limit for Expires
- Re: #290: Motivate one-year limit for Expires
- Re: #290: Motivate one-year limit for Expires
#297: p1 7.2.4: retrying requests
Call for feedback on web origin spec (was: Fwd: [websec] WG Last Call on draft-ietf-websec-origin-02 until Aug-15)
Re: If-Range and cache validation using Last-Modified
- #304, was: If-Range and cache validation using Last-Modified
- Re: If-Range and cache validation using Last-Modified
#160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Remaining issues related to redirects
- Re: Remaining issues related to redirects [#43 #295]
- Re: Remaining issues related to redirects [#43 #295]
- Re: Remaining issues related to redirects [#43 #295]
- Re: Remaining issues related to redirects [#43 #295]
- Re: #160: Redirects and non-GET methods
- Re: Remaining issues related to redirects [#43 #295]
- Re: Remaining issues related to redirects [#43 #295]
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
- Re: #160: Redirects and non-GET methods
Re: #285: Strength of requirements on Accept re: 406
- Re: #285: Strength of requirements on Accept re: 406
#300: Define non-final responses
- Re: #300: Define non-final responses
- Re: #300: Define non-final responses
- Re: #300: Define non-final responses
- Re: #300: Define non-final responses
Warnings and SHOULD
#100: DNS Spoofing / Rebinding
Content-Range on responses other than 206
- Re: Content-Range on responses other than 206
- #301: Content-Range on responses other than 206
- Re: Content-Range on responses other than 206
Generic semantics for the 400 status code
- Re: Generic semantics for the 400 status code
- #303: Generic semantics for the 400 status code (also #302)
Issues addressed in the -15 drafts
API Pagination limit
httpbis -15 drafts
Re: Content-Disposition status
URI equivalence and query parameter sequence
I-D ACTION:draft-ietf-httpbis-p2-semantics-15.txt
I-D ACTION:draft-ietf-httpbis-p3-payload-15.txt
I-D ACTION:draft-ietf-httpbis-p4-conditional-15.txt
I-D ACTION:draft-ietf-httpbis-p5-range-15.txt
I-D ACTION:draft-ietf-httpbis-p6-cache-15.txt
I-D ACTION:draft-ietf-httpbis-p7-auth-15.txt
I-D ACTION:draft-ietf-httpbis-p1-messaging-15.txt
I-D Action: draft-ietf-httpbis-method-registrations-06.txt
1xx response semantics
- Re: 1xx response semantics
- Re: 1xx response semantics
- Re: 1xx response semantics
Media-type containing semi-colon but no parameter
help
Re: Whitespace before responses
Re: Redirects and headers
Re: #295: Applying original fragment to "plain" redirected URI (also #43)
Re: #282: Recommend minimum sizes for protocol elements
Re: #288: Considering messages in isolation
Re: #231: Considerations for new headers
Re: status code for header fields to big
- Re: status code for header fields to big
- Re: status code for header fields to big
- Re: status code for header fields to big
- Re: status code for header fields to big