Thursday, 30 September 2010
Wednesday, 29 September 2010
- Re: Issue 160 (Redirects and non-GET methods)
- Re: Issue 160 (Redirects and non-GET methods)
- Re: Issue 160 (Redirects and non-GET methods)
- Re: Issue 160 (Redirects and non-GET methods)
- 403 description clarifications
Tuesday, 28 September 2010
- WG Action: RECHARTER: Hypertext Transfer Protocol Bis (httpbis)
- Re: Issue 141: "should we have an auth scheme registry"
- Re: Issue 141: "should we have an auth scheme registry"
- Re: Issue 141: "should we have an auth scheme registry"
Saturday, 25 September 2010
- Re: draft-bryan-metalinkhttp-18.txt
- Re: Link Relation Registry initial contents
- Re: Link Relation Registry initial contents
Friday, 24 September 2010
Thursday, 23 September 2010
- Specific non-2616 MS RFC implementation
- Re: Unifying & standardizing X-Moz & X-Purpose headers
- Re: Unifying & standardizing X-Moz & X-Purpose headers
- Unifying & standardizing X-Moz & X-Purpose headers
- Re: [#95] Multiple Content-Lengths
- Link Relation Registry initial contents
- IANA hanges to draft-nottingham-http-link-header
Wednesday, 22 September 2010
- Re: [#95] Multiple Content-Lengths
- Re: parsing of unknown challenges, was: Ticket 237
- Multiple Content-Type headers (was: Re: [#95] Multiple Content-Lengths)
- Re: Multiple content-types, was: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Multiple content-types, was: [#95] Multiple Content-Lengths
- Re: Issue 160 (Redirects and non-GET methods)
- Re: Issue 160 (Redirects and non-GET methods)
- Re: Issue 160 (Redirects and non-GET methods)
- Re: [#95] Multiple Content-Lengths
- Re: Issue 160 (Redirects and non-GET methods)
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- [Fwd: I-D Action:draft-ietf-kitten-digest-to-historic-02.txt]
- Re: [#177] Realm required on challenges
- Re: [#177] Realm required on challenges
- Re: parsing of unknown challenges, was: Ticket 237
- Re: parsing of unknown challenges, was: Ticket 237
- parsing of unknown challenges, was: Ticket 237
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- I-D Action:draft-ietf-httpbis-content-disp-02.txt
- Re: [#177] Realm required on challenges
Tuesday, 21 September 2010
- Re: Issue 160 (Redirects and non-GET methods)
- 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: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
Monday, 20 September 2010
- Re: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- Re: Issue 160 (Redirects and non-GET methods)
- Re: [#232] User-Agent Guidelines (proposal)
- Re: [#232] User-Agent Guidelines (proposal)
- Re: New issue: p5-range 5.4.2, proxy recommendations regarding 200 responses to Range
- Re: [#232] User-Agent Guidelines (proposal)
- Re: [#95] Multiple Content-Lengths
- Re: [#232] User-Agent Guidelines (proposal)
- Re: [#232] User-Agent Guidelines (proposal)
- Re: [#95] Multiple Content-Lengths
- [#232] User-Agent Guidelines (proposal)
- 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: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- RE: [#95] Multiple Content-Lengths
- Re: [#95] Multiple Content-Lengths
- [#95] Multiple Content-Lengths
Sunday, 19 September 2010
Thursday, 16 September 2010
- Re: I-D Action:draft-ietf-httpbis-content-disp-01.txt
- how to handle "Not Yet Available"?
- I-D Action:draft-ietf-httpbis-content-disp-01.txt
Wednesday, 15 September 2010
- ticket #78 (Relationship between 401, Authorization and WWW-Authenticate)
- Re: Issue 141: "should we have an auth scheme registry"
- Re: Comments on draft-ietf-httpbis-content-disp-00.txt
- Re: Issue 141: "should we have an auth scheme registry"
- Re: Protocol switch before, or after the 101 response?
- Re: Protocol switch before, or after the 101 response?
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
- Re: Comments on draft-ietf-httpbis-content-disp-00.txt
- Re: Issues addressed in the -10 and -11 drafts
- Re: Issues addressed in the -10 and -11 drafts
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
- Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Tuesday, 14 September 2010
- WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
- Re: Issues addressed in the -10 and -11 drafts
- Re: [#177] Realm required on challenges
- Re: Issues addressed in the -10 and -11 drafts
- Re: Issues addressed in the -10 and -11 drafts
- Re: Issues addressed in the -10 and -11 drafts
Monday, 13 September 2010
- Issue 141: "should we have an auth scheme registry"
- Issue 195, was: Proposed RFC 2617 erratum, Re: Backwards definition of authentication header
- Re: Ticket 237 (absorbing more of 2617), was: Minutes for Maastricht
- No WG meeting at IETF 79
Sunday, 12 September 2010
Saturday, 11 September 2010
- Re: Protocol switch before, or after the 101 response?
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Comments on draft-ietf-httpbis-content-disp-00.txt
- Protocol switch before, or after the 101 response?
Wednesday, 8 September 2010
- re: effective request URI/target URI, issues 221 & 222, was: Issues addressed, by the -10 drafts
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
Tuesday, 7 September 2010
Monday, 6 September 2010
- Re: I-D Action:draft-ietf-httpbis-content-disp-00.txt
- Re: effective request URI/target URI, issues 221 & 222, was: Issues addressed by the -10 drafts
- Re: I-D Action:draft-ietf-httpbis-content-disp-00.txt
Sunday, 5 September 2010
- Re: I-D Action:draft-ietf-httpbis-content-disp-00.txt
- Re: POST with empty body
- Re: remove/deprecate User-Agent header?
- Re: conditional-request implementation feedback
Saturday, 4 September 2010
- Issue 123 (factor out Content-Disposition), was: I-D Action:draft-ietf-httpbis-content-disp-00.txt
- Re: I-D Action:draft-ietf-httpbis-content-disp-00.txt
- I-D Action:draft-ietf-httpbis-content-disp-00.txt
Friday, 3 September 2010
- Re: POST with empty body
- Re: I-D Action:draft-reschke-rfc2183-in-http-03.txt [ new WG item ]
- Re: POST with empty body
Thursday, 2 September 2010
- Re: POST with empty body
- Re: POST with empty body
- Re: POST with empty body
- POST with empty body
- Re: Issues addressed in the -10 and -11 drafts
- Issues addressed in the -10 and -11 drafts
- Re: New issue: p5-range 5.4.2, proxy recommendations regarding 200 responses to Range
Wednesday, 1 September 2010
- Re: IPR Disclosure: CNRS's Statement about IPR related to RFC 4768, RFC 2069, RFC 4169, and draft-ietf-httpbis-p7-auth-11
- Re: IPR Disclosure: CNRS's Statement about IPR related to RFC 4768, RFC 2069, RFC 4169, and draft-ietf-httpbis-p7-auth-11
- RE: IPR Disclosure: CNRS's Statement about IPR related to RFC 4768, RFC 2069, RFC 4169, and draft-ietf-httpbis-p7-auth-11
- Re: IPR Disclosure: CNRS's Statement about IPR related to RFC 4768, RFC 2069, RFC 4169, and draft-ietf-httpbis-p7-auth-11
Tuesday, 31 August 2010
- IPR Disclosure: CNRS's Statement about IPR related to RFC 4768, RFC 2069, RFC 4169, and draft-ietf-httpbis-p7-auth-11
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Fwd: I-D Action:draft-reschke-rfc2183-in-http-03.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
Sunday, 29 August 2010
Friday, 27 August 2010
Thursday, 26 August 2010
- Re: Charter revision
- Issue 241 conditional header eval order, was: conditional-request implementation feedback
- Re: Charter revision
Wednesday, 25 August 2010
- Re: Charter revision
- Re: Charter revision
- Re: Charter revision
- Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.txt
- Charter revision
- Issue: expect 100-continue in HTTP/1.0 requests
Tuesday, 24 August 2010
- Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.txt
- Re: Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.txt
- Re: User confirmation and 307 redirects
- Fwd: I-D Action:draft-reschke-rfc2183-in-http-02.txt
- conditional-request implementation feedback
Monday, 23 August 2010
Friday, 20 August 2010
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects [#238]
- Re: User confirmation and 307 redirects [#238]
- Re: User confirmation and 307 redirects [#238]
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
Thursday, 19 August 2010
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: remove/deprecate User-Agent header?
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: remove/deprecate User-Agent header?
- Re: remove/deprecate User-Agent header?
- Re: remove/deprecate User-Agent header?
- Re: remove/deprecate User-Agent header?
- Re: User confirmation and 307 redirects
- remove/deprecate User-Agent header?
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Re: User confirmation and 307 redirects
- Fwd: I-D Action:draft-nottingham-http-portal-01.txt
- Re: I-D Action:draft-nottingham-http-portal-00.txt
Wednesday, 18 August 2010
- Re: User confirmation and 307 redirects
- User confirmation and 307 redirects
- Re: Fwd: I-D Action:draft-nottingham-http-portal-00.txt
Monday, 16 August 2010
- Re: Fwd: I-D Action:draft-reschke-basicauth-enc-01.txt
- Re: Fwd: I-D Action:draft-reschke-basicauth-enc-01.txt
- Fwd: I-D Action:draft-reschke-basicauth-enc-01.txt
Friday, 13 August 2010
- Re: RFC 5987 on Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
- Fwd: RFC 5987 on Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters
- Re: Proposal for work on an efficient, browser-friendly, HTTP-based communication protocol for fine-grained information exchange
Thursday, 12 August 2010
- Scope of body in an OPTIONS response
- Re: Fwd: Proposal for work on an efficient, browser-friendly, HTTP-based communication protocol for fine-grained information exchange
- Fwd: Proposal for work on an efficient, browser-friendly, HTTP-based communication protocol for fine-grained information exchange
Wednesday, 11 August 2010
- Fwd: I-D Action:draft-reschke-basicauth-enc-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
- RE: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: I-D Action:draft-nottingham-http-pipeline-00.txt
- RE: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
Tuesday, 10 August 2010
- Re: rewritten section on message body and length
- Re: Ticket 237 (absorbing more of 2617), was: Minutes for Maastricht
- Re: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
- RE: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
- Re: Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
- Fwd: I-D Action:draft-nottingham-http-pipeline-00.txt
Friday, 6 August 2010
Thursday, 5 August 2010
- Re: I-D Action:draft-nottingham-http-portal-00.txt
- Fwd: I-D Action:draft-nottingham-http-portal-00.txt
Wednesday, 4 August 2010
- http URI grammar
- HTTPbis -11 drafts published
- I-D Action:draft-ietf-httpbis-p6-cache-11.txt
- I-D Action:draft-ietf-httpbis-p7-auth-11.txt
- I-D Action:draft-ietf-httpbis-p5-range-11.txt
- I-D Action:draft-ietf-httpbis-p4-conditional-11.txt
- I-D Action:draft-ietf-httpbis-p3-payload-11.txt
- I-D Action:draft-ietf-httpbis-p2-semantics-11.txt
- I-D Action:draft-ietf-httpbis-p1-messaging-11.txt
- Request for feedback on HTTP Streaming overview (draft-wu-http-streaming-optimization-ps)
Tuesday, 3 August 2010
Thursday, 29 July 2010
- Re: Migrating CONNECT and Upgrade details from RFC2817
- Re: issue 79: must understand content-* header fields or fail
- Re: Migrating CONNECT and Upgrade details from RFC2817
- RE: Migrating CONNECT and Upgrade details from RFC2817
- Re: disallowing userinfo in http and https URIs
- Re: NEW: #225: PUT and DELETE invalidation vs. staleness
- Migrating CONNECT and Upgrade details from RFC2817
- Re: NEW: #225: PUT and DELETE invalidation vs. staleness
- Re: NEW: #225: PUT and DELETE invalidation vs. staleness
- Re: Ticket 237 (absorbing more of 2617), was: Minutes for Maastricht
Wednesday, 28 July 2010
- Ticket 237 (absorbing more of 2617), was: Minutes for Maastricht
- Re: disallowing userinfo in http and https URIs
- Re: disallowing userinfo in http and https URIs
- sending Last-Modified in 304 and 206 responses
- Re: disallowing userinfo in http and https URIs
- rewritten section on Content-Location
- Re: disallowing userinfo in http and https URIs
- Re: rewritten section on message body and length
- Re: disallowing userinfo in http and https URIs
- rewritten section on message body and length
- Re: disallowing userinfo in http and https URIs
- Re: disallowing userinfo in http and https URIs
- Re: disallowing userinfo in http and https URIs
- disallowing userinfo in http and https URIs
Tuesday, 27 July 2010
Monday, 26 July 2010
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: Revised Maastricht Agenda
- Reminder: HTTPbis WG meeting today
Sunday, 25 July 2010
- Re: NEW: #235: Cache Invalidation only happens upon successful responses
- Re: proposal for issue #178
- RE: #233 - Is * usable as a request-uri for new methods?
- Re: #233 - Is * usable as a request-uri for new methods?
Saturday, 24 July 2010
- RE: #233 - Is * usable as a request-uri for new methods?
- Re: #122 (MIME-Version not listed in P1, general header fields)
- NEW: #235: Cache Invalidation only happens upon successful responses
- Forcing validation
- Re: NEW: #233 - Is * usable as a request-uri for new methods?
- NEW: #233 - Is * usable as a request-uri for new methods?
- Re: [#203] Max-forwards and extension methods
Friday, 23 July 2010
- Issue 208, was: Issues addressed by the -10 drafts
- NEW: #224 - Header Classifications
- NEW: #223: Allowing heuristic freshness for new status codes
- NEW: #225: PUT and DELETE invalidation vs. staleness
- Issue 39, was: Issues addressed by the -10 drafts
- Re: New issue: p5-range 5.4.2, proxy recommendations regarding 200 responses to Range
- A note about the issues list and editorial workflow
- issue 226, "proxies not supporting certain methods"
- Re: proposal for issue #178
- Re: Revised Maastricht Agenda
- Re: effective request URI/target URI, issues 221 & 222, was: Issues addressed by the -10 drafts
- effective request URI/target URI, issues 221 & 222, was: Issues addressed by the -10 drafts
Thursday, 22 July 2010
Wednesday, 21 July 2010
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
- Re: Revised Maastricht Agenda
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
Tuesday, 20 July 2010
Monday, 19 July 2010
- Revised Maastricht Agenda
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
- Re: Issue 146, was: Users with different access rights in HTTP Authentication
- Issue 146, was: Users with different access rights in HTTP Authentication
Friday, 16 July 2010
- Re: Clarification on use of Content-Location header
- Re: Clarification on use of Content-Location header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- RE: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
Thursday, 15 July 2010
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: Clarification on use of Content-Location header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published : Connection header
- Re: parsing decimals, was: HTTPbis -10 drafts published
Wednesday, 14 July 2010
- Re: Clarification on use of Content-Location header
- Re: [#193] Trailers and intermediaries
- Re: parsing decimals, was: HTTPbis -10 drafts published
- parsing decimals, was: HTTPbis -10 drafts published
- Re: HTTPbis -10 drafts published : Connection header
- Re: HTTPbis -10 drafts published
- Re: HTTPbis -10 drafts published
- Re: [#193] Trailers and intermediaries
- Re: HTTPbis -10 drafts published
- Re: Clarification on use of Content-Location header
- Re: Clarification on use of Content-Location header
- Re: HTTPbis -10 drafts published
- Re: HTTPbis -10 drafts published
- Re: Clarification on use of Content-Location header
- Re: issue 79: must understand content-* header fields or fail
- Re: HTTPbis -10 drafts published
- [#203] Max-forwards and extension methods
- [#193] Trailers and intermediaries
- Re: [#208] IANA registry for cache-control directives
Tuesday, 13 July 2010
Monday, 12 July 2010
- I-D Action:draft-ietf-httpbis-method-registrations-04.txt
- I-D Action:draft-ietf-httpbis-p6-cache-10.txt
- I-D Action:draft-ietf-httpbis-p7-auth-10.txt
- I-D Action:draft-ietf-httpbis-p5-range-10.txt
- I-D Action:draft-ietf-httpbis-p2-semantics-10.txt
- I-D Action:draft-ietf-httpbis-p3-payload-10.txt
- I-D Action:draft-ietf-httpbis-p4-conditional-10.txt
- I-D Action:draft-ietf-httpbis-p1-messaging-10.txt
- DRAFT HTTPbis agenda for Maastricht
Friday, 9 July 2010
- Re: I-D Action:draft-loreto-http-timeout-00.txt
- Re: httpbis-p2 : 1xx messages may not always be treated as 100
- Re: httpbis-p2 : 1xx messages may not always be treated as 100
- Re: I-D Action:draft-loreto-http-timeout-00.txt
- Re: I-D Action:draft-loreto-http-timeout-00.txt
- RE: I-D Action:draft-loreto-http-timeout-00.txt
- Re: I-D Action:draft-loreto-http-timeout-00.txt
Thursday, 8 July 2010
- Re: NEW: value space of status codes [#213]
- Re: NEW: value space of status codes [#213]
- Re: NEW: value space of status codes [#213]
- Re: NEW: value space of status codes [#213]
- Re: NEW: value space of status codes [#213]
- Re: NEW: value space of status codes [#213]
- Re: NEW: value space of status codes [#213]
Wednesday, 7 July 2010
Tuesday, 6 July 2010
- httpbis-p2 : 1xx messages may not always be treated as 100
- RE: I-D Submission: draft-lee-httpext-metadata-00.txt
Sunday, 4 July 2010
- Re: I-D Submission: draft-lee-httpext-metadata-00.txt
- RE: I-D Submission: draft-lee-httpext-metadata-00.txt
- RE: I-D Submission: draft-lee-httpext-metadata-00.txt