Sunday, 30 September 2007
Saturday, 29 September 2007
Friday, 28 September 2007
- Re: range header query
- new issue: remove redundant MUST obey xrefs
- range header query
- Request to join http-wg
Tuesday, 18 September 2007
Saturday, 15 September 2007
Thursday, 13 September 2007
Wednesday, 12 September 2007
- Re: [saag] Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: mandatory draft sections (was Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt))
Tuesday, 11 September 2007
- Required doc sections (Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt))
- Re: [saag] [Ietf-http-auth] Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: Next step on web phishingdraft(draft-hartman-webauth-phishing-05.txt)
- RE: Next step on web phishingdraft(draft-hartman-webauth-phishing-05.txt)
- Re: Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
- Re: Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
- Re: Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
- RE: Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
- RE: Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
Monday, 10 September 2007
- Re: [saag] [Ietf-http-auth] Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- RE: [Ietf-http-auth] Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: [saag] Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
Sunday, 9 September 2007
- Re: Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
Monday, 10 September 2007
- RE: Next step on web phishing draft(draft-hartman-webauth-phishing-05.txt)
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
Sunday, 9 September 2007
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Ietf-http-auth] Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
Saturday, 8 September 2007
- Re: [saag] [Ietf-http-auth] Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: [Ietf-http-auth] Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Next step on web phishing draft (draft-hartman-webauth-phishing-05.txt)
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Fwd: semantic error in RFC 2616
Friday, 7 September 2007
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
Thursday, 6 September 2007
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: (XMLHttpRequest 2) Third proposal for cross-site extensions to XMLHttpRequest
- Re: Fwd: (XMLHttpRequest 2) Third proposal for cross-site extensions to XMLHttpRequest
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Fwd: (XMLHttpRequest 2) Third proposal for cross-site extensions to XMLHttpRequest
Wednesday, 5 September 2007
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
- Fwd: update "Authoritative Metadata"/ contentTypeOverride-24 based on HTML 5 spec?
Tuesday, 4 September 2007
Monday, 3 September 2007
Sunday, 2 September 2007
- NEW ISSUE (?): LINK header
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
Saturday, 1 September 2007
Friday, 31 August 2007
Thursday, 30 August 2007
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
Wednesday, 29 August 2007
- Re: HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- RE: Custom Ranges
Tuesday, 28 August 2007
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
Monday, 27 August 2007
- Re: HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
- Re: thinking about etags
- RE: thinking about etags
Sunday, 26 August 2007
Saturday, 25 August 2007
- [Fwd: Nomcom 2007-8: Please nominate candidates for IESG and IAB positions (Deadline: Sep 10, 2007)]
Friday, 24 August 2007
- Custom Ranges
- RE: Should a DELETE against a non-existent resource return a 2xx code?
- RE: Should a DELETE against a non-existent resource return a 2xx code?
Thursday, 23 August 2007
Wednesday, 22 August 2007
- [Fwd: I-D ACTION:draft-dusseault-http-patch-09.txt]
- Re: Should a DELETE against a non-existent resource return a 2xx code?
- Re: thinking about etags
- Re: [RFC] Optional header negotitation
- Re: WWW-Authenticate, Authorization and 401's
Tuesday, 21 August 2007
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: [RFC] Optional header negotitation
- RE: [RFC] Optional header negotitation
- Re: [RFC] Optional header negotitation
- RE: [RFC] Optional header negotitation
Monday, 20 August 2007
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Should a DELETE against a non-existent resource return a 2xx code?
- Should a DELETE against a non-existent resource return a 2xx code?
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: [RFC] Optional header negotitation
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter forhttp-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter forhttp-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Conneg for media types [was: HTTP Information Request]
- RE: [RFC] Optional header negotitation
- Re: Warnings
- Character encodings in headers [i74][was: Straw-man charter for http-bis]
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: Clarification of the term "deflate"
- Re: 305 Use Proxy deprecated?
- Re: HTTP version numbers returned by proxies
- Warnings
- Re: Straw-man charter for http-bis
- Re: New issue: Need for an HTTP request method registry
- Re: Message delimiting security issues
- Re: NEW ISSUE: Content-Location vs PUT/POST
- Re: WWW-Authenticate, Authorization and 401's
Sunday, 19 August 2007
Saturday, 18 August 2007
- RE: [RFC] Optional header negotitation
- Re: thinking about etags
- Re: [RFC] Optional header negotitation
- Re: Definition of "variant" and "requested variant", was: New "200 OK" status codes, PATCH & PROPFIND
- Re: Definition of "variant" and "requested variant", was: New "200 OK" status codes, PATCH & PROPFIND
- RE: [RFC] Optional header negotitation
- thinking about etags
- Re: [RFC] Optional header negotitation
- Re: Definition of "variant" and "requested variant", was: New "200 OK" status codes, PATCH & PROPFIND
- Re: Definition of "variant" and "requested variant", was: New "200 OK" status codes, PATCH & PROPFIND
Friday, 17 August 2007
- RE: [RFC] Optional header negotitation
- Re: WWW-Authenticate, Authorization and 401's
- Definition of "variant" and "requested variant", was: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- [RFC] Optional header negotitation
- Re: WWW-Authenticate, Authorization and 401's
- Re: WWW-Authenticate, Authorization and 401's
- Re: WWW-Authenticate, Authorization and 401's
- RE: Clarification of the term "deflate"
- Re: WWW-Authenticate, Authorization and 401's
Monday, 13 August 2007
- Re: Patch options -- summary of recent conversations
- Re: Trailers and intermediaries
- Re: Patch options -- summary of recent conversations
- Trailers and intermediaries
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: Patch options -- summary of recent conversations
- Re: HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
Sunday, 12 August 2007
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
- Re: HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
Saturday, 11 August 2007
- Re: Revised charter proposal
- HTTPBis BOF followup - should RFC 2965 (cookie) be in scope for the WG?
- HTTPBis BOF followup - should RFC 2817/2818 be in scope for the WG?
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
Friday, 10 August 2007
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: Patch options -- summary of recent conversations
- Re: New issue: Need for an HTTP request method registry
- Patch options -- summary of recent conversations
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: Resend: HTTP Performance extension for NAV(network-based anti-virus) systems
Thursday, 9 August 2007
- Re: New issue: Need for an HTTP request method registry
- Re: Clarification of the term "deflate"
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: Clarification of the term "deflate"
- Re: New issue: Need for an HTTP request method registry
- Re: Clarification of the term "deflate"
- New issue: 15.3 misguided?
Wednesday, 8 August 2007
- Re: New issue: Need for an HTTP request method registry
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: revised I-D draft-decroy-http-progress-01
- RE: Clarification of the term "deflate"
- Re: Metalink: higher availability and self repairing downloads
Tuesday, 7 August 2007
- Re: Clarification of the term "deflate"
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- RE: Clarification of the term "deflate"
- RE: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- RE: Clarification of the term "deflate"
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: Clarification of the term "deflate"
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: revised I-D draft-decroy-http-progress-01
- Clarification of the term "deflate"
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
Monday, 6 August 2007
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: New issue: Need for an HTTP request method registry
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- New issue: Need for an HTTP request method registry
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: Resend: HTTP Performance extension for NAV(network-based anti-virus) systems
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: Resend: HTTP Performance extension for NAV(network-based anti-virus) systems
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: Fodder for security issues document (was: dns binding)
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: Fodder for security issues document (was: dns binding)
- Re: PATCH, Expect, Prefer, etc
- Re: New "200 OK" status codes, PATCH & PROPFIND
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: PATCH, Expect, Prefer, etc
- New "200 OK" status codes, PATCH & PROPFIND
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: PATCH, Expect, Prefer, etc
- Re: Fodder for security issues document (was: dns binding)
Saturday, 4 August 2007
Friday, 3 August 2007
- Re: Draft minutes from HTTPBis BOF
- Re: Draft minutes from HTTPBis BOF
- Re: PATCH, Expect, Prefer, etc
- Re: PATCH, Expect, Prefer, etc
- Re: PATCH, Expect, Prefer, etc
- Re: PATCH, Expect, Prefer, etc
- Re: PATCH, Expect, Prefer, etc
- Re: PATCH, Expect, Prefer, etc
- Re: Draft minutes from HTTPBis BOF
- Re: Resend: HTTP Performance extension for NAV(network-based anti-virus) systems
- Re: PATCH, Expect, Prefer, etc
- Re: PATCH, Expect, Prefer, etc
- PATCH, Expect, Prefer, etc
- revised I-D draft-decroy-http-progress-01
- Re: Resend: HTTP Performance extension for NAV(network-based anti-virus) systems
Thursday, 2 August 2007
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- RE: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Fodder for security issues document (was: dns binding)
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
Wednesday, 1 August 2007
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Draft minutes from HTTPBis BOF
Tuesday, 31 July 2007
Wednesday, 1 August 2007
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
Tuesday, 31 July 2007
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: NEW ISSUE: Content-Location vs PUT/POST
- Re: NEW ISSUE: Content-Location vs PUT/POST
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: NEW ISSUE: Content-Location vs PUT/POST
- Re: I-D ACTION:draft-reschke-http-get-location-00.txt
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- NEW ISSUE: Content-Location vs PUT/POST
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
Monday, 30 July 2007
Friday, 27 July 2007
- Re: NEW ISSUE: Content-* headers vs PUT
- RE: Revised charter proposal
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Revised charter proposal
- Re: Revised charter proposal
- Re: Revised charter proposal
- Re: Suggestion for NEW Issue: Pipelining problems
Thursday, 26 July 2007
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: NEW ISSUE: Content-* headers vs PUT
- Resend: HTTP Performance extension for NAV(network-based anti-virus) systems
- [ietf-http-wg] <none>
- Re: Suggestion for NEW Issue: Pipelining problems
- Revised charter proposal
- BoF Summary
- WWW-Authenticate, Authorization and 401's
Wednesday, 25 July 2007
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: NEW ISSUE: Content-* headers vs PUT
- Re: NEW ISSUE: Content-* headers vs PUT
- NEW ISSUE: Content-* headers vs PUT
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Comments on draft-dusseault-http-patch-08, was: [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
Tuesday, 24 July 2007
Monday, 23 July 2007
- Re: Suggestion for NEW Issue: Pipelining problems
- [Fwd: I-D ACTION:draft-dusseault-http-patch-08.txt]
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Draft agenda for the HTTPBis BOF
Saturday, 21 July 2007
Friday, 20 July 2007
Thursday, 19 July 2007
Wednesday, 18 July 2007
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
Tuesday, 17 July 2007
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- RE: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- RE: Suggestion for NEW Issue: Pipelining problems
- Re: Suggestion for NEW Issue: Pipelining problems
- Suggestion for NEW Issue: Pipelining problems
- Re: NEW ISSUE: example for matching functions, was: Weak and strong ETags
- Re: NEW ISSUE: example for matching functions, was: Weak and strong ETags
- Re: NEW ISSUE: clarify "requested variant"
- Re: NEW ISSUE: cacheability of status 303
Monday, 16 July 2007
Sunday, 15 July 2007
Saturday, 14 July 2007
Friday, 13 July 2007
Thursday, 12 July 2007
Wednesday, 11 July 2007
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
Tuesday, 10 July 2007
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
Monday, 9 July 2007
Friday, 6 July 2007
Thursday, 5 July 2007
- Re: PATCH Draft
- Re: PATCH Draft
- Re: Some comments on the PATCH draft
- Re: Some comments on the PATCH draft
- Re: PATCH Draft
Wednesday, 4 July 2007
- Re: PATCH Draft
- Re: I-D ACTION:draft-lafon-rfc2616bis-03.txt
- Re: PATCH Draft
- Re: PATCH Draft
- Re: PATCH Draft
- Re: PATCH Draft
- Re: Some comments on the PATCH draft
- Re: Standardizing Firefox's Implementation of Link Fingerprints
Tuesday, 3 July 2007
- Re: Some comments on the PATCH draft
- RE: Some comments on the PATCH draft
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- RE: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Some comments on the PATCH draft
- Some comments on the PATCH draft
- RE: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- RE: Standardizing Firefox's Implementation of Link Fingerprints
Monday, 2 July 2007
- Re: Standardizing Firefox's Implementation of Link Fingerprints
- Standardizing Firefox's Implementation of Link Fingerprints
- Re: RFC2616 vs RFC2617, was: Straw-man charter for http-bis
- Re: RFC2616 vs RFC2617, was: Straw-man charter for http-bis
- Re: RFC2616 vs RFC2617, was: Straw-man charter for http-bis
- Re: Regarding dynamic ip addressed for HTTP Servers.