Thursday, 31 March 2011
- link to old keep-alive notes
- httpbis wg followup - DOSETA discussion list
- Re: Updated Prague agenda / remote participation details
- draft-bryan-metalinkhttp-22 and redirects
Wednesday, 30 March 2011
Tuesday, 29 March 2011
Wednesday, 30 March 2011
- DOSETA discussion list
- Re: I-D Action:draft-snell-http-prefer-03.txt
- Re: I-D Action:draft-snell-http-prefer-03.txt
- RE: I-D Action:draft-snell-http-prefer-03.txt
- Re: I-D Action:draft-snell-http-prefer-03.txt
Tuesday, 29 March 2011
Monday, 28 March 2011
Tuesday, 29 March 2011
- Re: I-D Action:draft-snell-http-prefer-03.txt
- Re: I-D Action:draft-snell-http-prefer-03.txt
- Re: I-D Action:draft-snell-http-prefer-03.txt
- Re: Fwd: I-D Action:draft-snell-http-prefer-03.txt
- Fwd: I-D Action:draft-snell-http-prefer-03.txt
- Re: Feedback on draft-burke-content-signature-00.txt
- Re: Feedback on draft-burke-content-signature-00.txt
Monday, 28 March 2011
- FW: HTTP authentication side meeting
- Re: 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)
- 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)
- Re: I-D Action:draft-ietf-httpbis-content-disp-09.txt
- I-D Action:draft-ietf-httpbis-content-disp-09.txt
- RE: Feedback on draft-burke-content-signature-00.txt
Sunday, 27 March 2011
- Re: Implementation experience feeding into http://www.ietf.org/id/draft-nottingham-http-pipeline-01.txt?
- Re: [#95] Multiple Content-Lengths
- Re: Implementation experience feeding into http://www.ietf.org/id/draft-nottingham-http-pipeline-01.txt?
- Re: #178: Content-MD5 and partial responses
- Re: #178: Content-MD5 and partial responses
- Re: API Rate Limits and HTTP Code [#255]
- Re: [#95] Multiple Content-Lengths
- Re: Feedback on draft-burke-content-signature-00.txt
Friday, 25 March 2011
Thursday, 24 March 2011
- 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
Wednesday, 23 March 2011
Sunday, 27 March 2011
- Re: DOSETA and MIMEAUTH
- Re: #273: HTTP-Version should be redefined as fixed length pair of DIGIT . DIGIT
- #273: HTTP-Version should be redefined as fixed length pair of DIGIT . DIGIT
- Re: DOSETA and MIMEAUTH
- #104: Header Type Defaulting
- Re: About draft-nottingham-http-pipeline-01.txt
Saturday, 26 March 2011
Friday, 25 March 2011
- Re: Feedback on draft-burke-content-signature-00.txt
- RE: About draft-nottingham-http-pipeline-01.txt
- Implementation experience feeding into http://www.ietf.org/id/draft-nottingham-http-pipeline-01.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
Thursday, 24 March 2011
- 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
Wednesday, 23 March 2011
Tuesday, 22 March 2011
- [vixie@isc.org: googlebot to the rescue]
- Re: About draft-nottingham-http-pipeline-01.txt
- Re: About draft-nottingham-http-pipeline-01.txt
- Issues addressed in the -13 drafts
- Re: About draft-nottingham-http-pipeline-01.txt
Monday, 21 March 2011
Friday, 18 March 2011
Wednesday, 16 March 2011
Tuesday, 15 March 2011
- Re: About draft-nottingham-http-pipeline-01.txt
- 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
Monday, 14 March 2011
- Re: About draft-nottingham-http-pipeline-01.txt
- I-D Action:draft-ietf-httpbis-content-disp-08.txt
- About draft-nottingham-http-pipeline-01.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
Saturday, 12 March 2011
Friday, 11 March 2011
- more HTTP timeout comments
- Re: Introduction
- Re: Question on new PUT section
- Re: Introduction
- Re: Question on new PUT section
- Re: Question on new PUT section
- Question on new PUT section
- Introduction
Thursday, 10 March 2011
- Fwd: [hybi] Fwd: New Version Notification for draft-thomson-hybi-http-timeout-00
- Issue 281, was: Unclear example for private parameters on Accept headers
- Unclear example for private parameters on Accept headers
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
Wednesday, 9 March 2011
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: NEW: value space of status codes [#213]
Tuesday, 8 March 2011
Monday, 7 March 2011
- Re: Content-Disposition: LWS in parameter ABNF; was: ISSUE-280: whitespace in parameter syntax?
- FYI: MPEG Dash (adaptive streaming over HTTP)
- Fwd: I-D Action:draft-thomson-hybi-http-timeout-00.txt
- Re: "chunked" as non-final transfer-extension
- Re: Content-Disposition: LWS in parameter ABNF; was: ISSUE-280: whitespace in parameter syntax?
Sunday, 6 March 2011
- "chunked" as non-final transfer-extension
- Content-Disposition: LWS in parameter ABNF; was: ISSUE-280: whitespace in parameter syntax?
- Re: Link header is representation metadata?
- Re: Link header is representation metadata?
- ISSUE-280: whitespace in parameter syntax?
- 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
Thursday, 3 March 2011
Wednesday, 2 March 2011
Tuesday, 1 March 2011
- Re: conformance languages (issue 278),
- 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
Monday, 28 February 2011
- 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
- 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
Saturday, 26 February 2011
- Re: I-D Action:draft-ietf-httpbis-content-disp-06.txt
- I-D Action:draft-ietf-httpbis-content-disp-06.txt
- Re: Content-Disposition: *sender* advice
Friday, 25 February 2011
- Re: Content-Disposition: *sender* advice
- Re: Content-Disposition: *sender* advice
- Re: Content-Disposition: *sender* advice
- Fwd: HTTPBIS - Requested session has been scheduled for IETF 80
Thursday, 24 February 2011
Wednesday, 23 February 2011
- Re: Content-Disposition: *sender* advice
- Re: Content-Disposition: *sender* advice
- Re: Content-Disposition: *sender* advice
- Re: Content-Disposition: *sender* advice
- Re: Content-Disposition: *sender* advice
Tuesday, 22 February 2011
Monday, 21 February 2011
- Re: Sec-* headers
- Re: Sec-* headers
- Re: Sec-* headers
- Sec-* headers
- Re: [#95] Multiple Content-Lengths
- Re: NEW: value space of status codes [#213]
- Re: #268: Clarify "public"
Saturday, 19 February 2011
Friday, 18 February 2011
- Re: Draft on HTTP Warnings registry, was: Using extension points without registries
- Fwd: New Version Notification for draft-nottingham-http-portal-02
Thursday, 17 February 2011
- Re: #243: iso-8859-1 in C-D
- progress on Issue 137
- Re: I-D Action:draft-ietf-httpbis-content-disp-05.txt
- I-D Action:draft-ietf-httpbis-content-disp-05.txt
Wednesday, 16 February 2011
- Re: Content-Location: conformance and error handling
- Re: 409 Conflict - exposing more details
- Re: 409 Conflict - exposing more details
Tuesday, 15 February 2011
- Content-Disposition: *sender* advice
- Re: 409 Conflict - exposing more details
- Re: 409 Conflict - exposing more details
Monday, 14 February 2011
- Re: 409 Conflict - exposing more details
- Re: 409 Conflict - exposing more details
- Re: 409 Conflict - exposing more details
- Re: 409 Conflict - exposing more details
- 409 Conflict - exposing more details
Friday, 11 February 2011
- Re: Content-Location: path separator characters [#272]
- Re: Content-Location: conformance and error handling
Thursday, 10 February 2011
- Re: API Rate Limits and HTTP Code [#255]
- Content-Disposition: conformance and error handling, was: Content-Location: conformance and error handling
- Re: Content-Location: character set
- Re: Content-Location: character set
- Re: Content-Location: path separator characters [#272]
- Prague
- Re: Content-Location: character set
- Re: Content-Location: character set
- Re: API Rate Limits and HTTP Code [#255]
- Re: NEW: #225: PUT and DELETE invalidation vs. staleness
- Re: Does no-store in request imply no-cache? [#249]
- Re: Content-Location: character set
- Re: Content-Location: character set
- Content-Location: character set
- Re: Content-Location: path separator characters [#272]
- Content-Location: path separator characters
- Content-Location: conformance and error handling
Saturday, 5 February 2011
Friday, 4 February 2011
- Re: Content-Disposition cardinality / priority [was: TICKET 259: 'treat as invalid' not defined]
- Re: Does no-store in request imply no-cache? [#249]
- Re: Does no-store in request imply no-cache? [#249]
- FYI: using extension methods with Java's HttpURLConnection
- Re: \-decoding filename parameters [general issue now #270]
- Re: \-decoding filename parameters [general issue now #270]
- Re: \-decoding filename parameters [general issue now #270]
- Re: \-decoding filename parameters [general issue now #270]
- Re: \-decoding filename parameters [general issue now #270]
- Re: Does no-store in request imply no-cache? [#249]
Thursday, 3 February 2011
- 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]
- Re: \-decoding filename parameters [was: TICKET 259: 'treat as invalid' not defined]
- Re: Does no-store in request imply no-cache? [#249]
- Re: issues addressed in the -12 drafts
- 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]
- \-decoding filename parameters [was: TICKET 259: 'treat as invalid' not defined]
Tuesday, 1 February 2011
- Re: Link header is representation metadata?
- Re: Link header is representation metadata?
- Link header is representation metadata?
Saturday, 29 January 2011
- Re: API Rate Limits and HTTP Code [#255]
- Re: API Rate Limits and HTTP Code [#255]
- Re: API Rate Limits and HTTP Code [#255]
Friday, 28 January 2011
Wednesday, 26 January 2011
- Re: Content-Location q
- Fwd: Last Call for Navigation Timing API
- Re: [apps-discuss] For consideration as an appsawg document: draft-nottingham-http-portal
- Re: [apps-discuss] For consideration as an appsawg document: draft-nottingham-http-portal
- Re: Content-Location q
- Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation
- Re: API Rate Limits and HTTP Code [#255]
Friday, 21 January 2011
- Re: Final question on the topic of CL
- Re: Retry-After header on 20X response -- HTTP/1.1 spec extension?
- 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?
- Re: Content-Location q
- Re: Content-Location q
- Re: Content-Location q
- Re: Content-Location q
- Re: Content-Location q
- Re: Content-Location q
- 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)
Thursday, 20 January 2011
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: Indicating a resource does not exist
- Re: draft-bryan-metalinkhttp-18.txt
- Re: Status code questions
- Indicating a resource does not exist
- Re: Resource states (initial and final)
- Resource states (initial and final)
- Status code questions
Wednesday, 19 January 2011
- Re: draft-bryan-metalinkhttp-18.txt
- Re: draft-bryan-metalinkhttp-18.txt
- Re: draft-bryan-metalinkhttp-18.txt
- Re: draft-bryan-metalinkhttp-18.txt
- Re: draft-bryan-metalinkhttp-18.txt
- Re: draft-bryan-metalinkhttp-18.txt
- Re: draft-bryan-metalinkhttp-18.txt
Sunday, 16 January 2011
Friday, 14 January 2011
- fyi: DOSETA proposal in DKIM WG
- Re: [saag] [websec] [apps-discuss] [kitten] HTTP authentication: the next generation
Tuesday, 11 January 2011
- Draft on HTTP Warnings registry, was: Using extension points without registries
- Re: *NOT* using extension points without registries, was: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
Monday, 10 January 2011
- 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
Sunday, 9 January 2011
- 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] [http-auth] [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
- 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: [apps-discuss] [saag] [websec] [kitten] HTTP authentication: the next generation
Saturday, 8 January 2011
- 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: [Ietf-message-headers] Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- 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
- Last Call Summary on draft-yevstifeyev-http-headers-not-recognized
Friday, 7 January 2011
- Re: [http-auth] [websec] HTTP authentication: the next generation
- Re: [websec] HTTP authentication: the next generation
- Re: [websec] HTTP authentication: the next generation
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: Clarification on use of Content-Location requested
- Clarification on use of Content-Location requested
Thursday, 6 January 2011
- Re: I-D Action:draft-ietf-httpbis-method-registrations-05.txt
- Re: I-D Action:draft-ietf-httpbis-method-registrations-05.txt
- I-D Action:draft-ietf-httpbis-method-registrations-05.txt
- Re: [saag] [websec] [kitten] HTTP authentication: the next generation
- Re: [websec] [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: [kitten] [saag] HTTP authentication: the next generation