link to old keep-alive notes
httpbis wg followup - DOSETA discussion list
draft-bryan-metalinkhttp-22 and redirects
PUT and DELETE methods in 200 code
Fwd: I-D Action:draft-snell-http-prefer-03.txt
- Re: Fwd: I-D Action:draft-snell-http-prefer-03.txt
FW: HTTP authentication side meeting
Updated Prague agenda / remote participation details
Protocol Action: 'Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)' to Proposed Standard (draft-ietf-httpbis-content-disp-09.txt)
I-D Action:draft-ietf-httpbis-content-disp-09.txt
Re: #178: Content-MD5 and partial responses
#273: HTTP-Version should be redefined as fixed length pair of DIGIT . DIGIT
#104: Header Type Defaulting
DOSETA and MIMEAUTH
Implementation experience feeding into http://www.ietf.org/id/draft-nottingham-http-pipeline-01.txt?
Feedback on draft-burke-content-signature-00.txt
- RE: Feedback on draft-burke-content-signature-00.txt
- RE: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- RE: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- RE: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- RE: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- DOSETA discussion list
- RE: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- RE: Feedback on draft-burke-content-signature-00.txt
[vixie@isc.org: googlebot to the rescue]
Issues addressed in the -13 drafts
Preliminary agenda for Prague
I-D Action:draft-ietf-httpbis-content-disp-08.txt
Fwd: I-D Action:draft-nottingham-http-pipeline-01.txt
httpbis -13 drafts
I-D Action:draft-ietf-httpbis-p6-cache-13.txt
I-D Action:draft-ietf-httpbis-p7-auth-13.txt
I-D Action:draft-ietf-httpbis-p5-range-13.txt
I-D Action:draft-ietf-httpbis-p4-conditional-13.txt
I-D Action:draft-ietf-httpbis-p2-semantics-13.txt
I-D Action:draft-ietf-httpbis-p3-payload-13.txt
I-D Action:draft-ietf-httpbis-p1-messaging-13.txt
I-D Action:draft-ietf-httpbis-content-disp-07.txt
more HTTP timeout comments
Question on new PUT section
Introduction
Fwd: [hybi] Fwd: New Version Notification for draft-thomson-hybi-http-timeout-00
Unclear example for private parameters on Accept headers
FYI: MPEG Dash (adaptive streaming over HTTP)
Fwd: I-D Action:draft-thomson-hybi-http-timeout-00.txt
"chunked" as non-final transfer-extension
ISSUE-280: whitespace in parameter syntax?
Fwd: [http-state] Protocol Action: 'HTTP State Management Mechanism' to Proposed Standard (draft-ietf-httpstate-cookie-23.txt)
Re: conformance languages (issue 278), was: Last Call: <draft-ietf-httpbis-content-disp-06.txt> (Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)) to Proposed Standard
Re: conformance languages (issue 278),
Last Call: <draft-ietf-httpbis-content-disp-06.txt> (Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)) to Proposed Standard
- Re: Last Call: <draft-ietf-httpbis-content-disp-06.txt> (Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)) to Proposed Standard
- Re: Last Call: <draft-ietf-httpbis-content-disp-06.txt> (Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)) to Proposed Standard
Re: Working Group Last Call: draft-ietf-httpbis-content-disp-02
I-D Action:draft-ietf-httpbis-content-disp-06.txt
Fwd: HTTPBIS - Requested session has been scheduled for IETF 80
Sec-* headers
Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
Re: NEW: value space of status codes [#213]
Fwd: New Version Notification for draft-nottingham-http-portal-02
Re: #243: iso-8859-1 in C-D
progress on Issue 137
I-D Action:draft-ietf-httpbis-content-disp-05.txt
Content-Disposition: *sender* advice
- Re: Content-Disposition: *sender* advice
409 Conflict - exposing more details
Prague
Content-Location: character set
Content-Location: path separator characters
Content-Location: conformance and error handling
- Content-Disposition: conformance and error handling, was: Content-Location: conformance and error handling
- Re: Content-Location: conformance and error handling
FYI: using extension methods with Java's HttpURLConnection
Re: NEW: #225: PUT and DELETE invalidation vs. staleness
Re: NEW: #235: Cache Invalidation only happens upon successful responses
Re: Does no-store in request imply no-cache? [#249]
#268: Clarify "public"
issues addressed in the -12 drafts
Content-Disposition cardinality / priority [was: TICKET 259: 'treat as invalid' not defined]
- Re: Content-Disposition cardinality / priority [was: TICKET 259: 'treat as invalid' not defined]
- Re: Content-Disposition cardinality / priority [was: TICKET 259: 'treat as invalid' not defined]
\-decoding filename parameters [was: TICKET 259: 'treat as invalid' not defined]
Link header is representation metadata?
Fwd: Last Call for Navigation Timing API
Re: [apps-discuss] For consideration as an appsawg document: draft-nottingham-http-portal
Final question on the topic of CL
Re: API Rate Limits and HTTP Code [#255]
Re: Retry-After header on 20X response -- HTTP/1.1 spec extension?
Content-Location q
Fwd: Last Call: <draft-bryan-metalinkhttp-19.txt> (Metalink/HTTP: Mirrors and Cryptographic Hashes in HTTP Header Fields) to Proposed Standard
Re: [hybi] OPTIONS (was Re: It's time to ship)
Indicating a resource does not exist
- Re: Indicating a resource does not exist
Resource states (initial and final)
Status code questions
Re: draft-bryan-metalinkhttp-18.txt
fyi: DOSETA proposal in DKIM WG
Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation
Re: *NOT* using extension points without registries, was: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
Re: [apps-discuss] [http-auth] [saag] [websec] [kitten] HTTP authentication: the next generation
Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Using extension points without registries, was: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: Using extension points without registries, was: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: Using extension points without registries, was: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
Re: [websec] HTTP authentication: the next generation
Clarification on use of Content-Location requested
I-D Action:draft-ietf-httpbis-method-registrations-05.txt
Re: [kitten] [saag] HTTP authentication: the next generation
- Re: [websec] [kitten] [saag] HTTP authentication: the next generation
- Re: [websec] [kitten] [saag] HTTP authentication: the next generation
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [websec] [kitten] [saag] HTTP authentication: the next generation