Tuesday, 30 December 2008
Friday, 26 December 2008
Wednesday, 24 December 2008
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Leading zeroes in 1*DIGIT productions
- Re: Leading zeroes in 1*DIGIT productions
Tuesday, 23 December 2008
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: HTTP 301 responses for POST
- RE: HTTP 301 responses for POST
- Re: HTTP 301 responses for POST
- Re: Retry-After header on 20X response -- HTTP/1.1 spec extension?
- Re: HTTP 301 responses for POST
- Re: Retry-After header on 20X response -- HTTP/1.1 spec extension?
- RE: HTTP 301 responses for POST
- Retry-After header on 20X response -- HTTP/1.1 spec extension?
- Re: Leading zeroes in 1*DIGIT productions
Monday, 22 December 2008
- Re: Updated Patch
- Re: Updated Patch
- Re: Updated Patch
- Re: Updated Patch
- RE: HTTP 301 responses for POST
Sunday, 21 December 2008
Friday, 19 December 2008
Sunday, 21 December 2008
Friday, 19 December 2008
Thursday, 18 December 2008
- Re: Leading zeroes in 1*DIGIT productions
- Re: Leading zeroes in 1*DIGIT productions
- Re: Leading zeroes in 1*DIGIT productions
- Re: Leading zeroes in 1*DIGIT productions
- Re: Base for first-byte-pos, last-byte-pos, suffix-length
- Re: Leading zeroes in 1*DIGIT productions
- Re: Leading zeroes in 1*DIGIT productions
- Leading zeroes in 1*DIGIT productions
- Base for first-byte-pos, last-byte-pos, suffix-length
Wednesday, 17 December 2008
- Re: HTTPOnly Cookies Specification
- Re: HTTPOnly Cookies Specification
- Re: HTTPOnly Cookies Specification
Monday, 15 December 2008
- Re: Removing multipart/byteranges as a message delimiter -- implementation survey [#90]
- Date header in cached responses
Sunday, 14 December 2008
- Re: Removing multipart/byteranges as a message delimiter -- implementation survey [#90]
- Re: Removing multipart/byteranges as a message delimiter -- implementation survey [#90]
Saturday, 13 December 2008
Friday, 12 December 2008
- RE: Use of the "Stale" flag in the WWW-Authenticate header
- Re: HTTPOnly Cookies Specification
- Re: RFC 3143
- Re: RFC 3143
- Re: RFC 3143
- Removing multipart/byteranges as a message delimiter -- implementation survey [#90]
Thursday, 11 December 2008
- Re: [rest-discuss] MIME properties instead +
- Re: Use of the "Stale" flag in the WWW-Authenticate header
- Re: #90: multipart/byteranges
- RE: Use of the "Stale" flag in the WWW-Authenticate header
- RFC 3143
- Re: RFC2231 encoding in HTTP: whitespace handling
- Re: #90: multipart/byteranges
- Re: [whatwg] Solving the login/logout problem in HTML
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: #90: multipart/byteranges
- Re: #90: multipart/byteranges
- Re: #90: multipart/byteranges
- Re: #90: multipart/byteranges
- Re: link relationship registration
- Re: #90: multipart/byteranges
- Re: #90: multipart/byteranges
Wednesday, 10 December 2008
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: #90: multipart/byteranges
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: #90: multipart/byteranges
- Re: #90: multipart/byteranges
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration
- Re: #90: multipart/byteranges
- Re: link relationship registration
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: link relationship registration
- Re: link relationship registration
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: #90: multipart/byteranges
Tuesday, 9 December 2008
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
Monday, 8 December 2008
- Re: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
Saturday, 6 December 2008
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
Friday, 5 December 2008
- Googles ResumableHttpRequestsProposal vs Microsoft BITS
- RE: Use of the "Stale" flag in the WWW-Authenticate header
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
Thursday, 4 December 2008
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
Wednesday, 3 December 2008
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Use of the "Stale" flag in the WWW-Authenticate header
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Remove elfius@gmail.com from the list, please
- RE: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
Tuesday, 2 December 2008
- Re: combining authenticated and anonymous access
- RE: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- RE: Feedback for draft-nottingham-http-link-header-03
- Re: Feedback for draft-nottingham-http-link-header-03
- Feedback for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- RE: New Version Notification for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: Cache key history
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- Re: New Version Notification for draft-nottingham-http-link-header-03
Monday, 1 December 2008
- Re: link relationship registration [was: New Version Notification for draft-nottingham-http-link-header-03]
- I-D ACTION:draft-ietf-httpbis-method-registrations-01.txt
- Re: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Feedback on draft-nottingham-http-link-header-03, was: Fwd: New Version Notification for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Re: New Version Notification for draft-nottingham-http-link-header-03
- Fwd: New Version Notification for draft-nottingham-http-link-header-03
Saturday, 29 November 2008
- Re: Content type for /site-meta (or HTTP header fragment format)
- FYI: draft-nottingham-http-stale-controls-00
Friday, 28 November 2008
- Re: Content type for /site-meta (or HTTP header fragment format)
- Cache key history
- Content type for /site-meta (or HTTP header fragment format)
- Re: combining authenticated and anonymous access
- Re: combining authenticated and anonymous access
- Re: combining authenticated and anonymous access
Thursday, 27 November 2008
- Re: combining authenticated and anonymous access
- RE: combining authenticated and anonymous access
- Are accept-extensions used in practice?
- combining authenticated and anonymous access
Wednesday, 26 November 2008
Monday, 24 November 2008
- The demise of the Netscape Doc??? Here is working linkRe: HTTPOnly Cookies Specification
- Re: HTTPOnly Cookies Specification
Sunday, 23 November 2008
- Re: HTTPOnly Cookies Specification
- Re: HTTPOnly Cookies Specification
- Re: HTTPOnly Cookies Specification
- Re: HTTPOnly Cookies Specification
Saturday, 22 November 2008
Friday, 21 November 2008
Thursday, 20 November 2008
- HTTPOnly Cookies Specification
- Re: draft -05 and current status
- RE: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
Wednesday, 19 November 2008
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching (proposal)
- Re: NEW ISSUE: Methods and Caching (proposal)
- Re: NEW ISSUE: Methods and Caching (proposal)
- RE: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
Tuesday, 18 November 2008
- RE: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching (proposal)
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: draft -05 and current status
- RE: NEW ISSUE: Methods and Caching
- Re: draft -05 and current status
- RE: NEW ISSUE: Methods and Caching
Monday, 17 November 2008
Tuesday, 18 November 2008
- RE: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
Monday, 17 November 2008
- Re: NEW ISSUE: Methods and Caching
- Re: draft -05 and current status
- Re: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
- RE: NEW ISSUE: Methods and Caching
- draft -05 and current status
- I-D Action:draft-ietf-httpbis-p7-auth-05.txt
- I-D Action:draft-ietf-httpbis-p4-conditional-05.txt
- I-D Action:draft-ietf-httpbis-p3-payload-05.txt
- I-D Action:draft-ietf-httpbis-p2-semantics-05.txt
- I-D Action:draft-ietf-httpbis-p5-range-05.txt
- I-D Action:draft-ietf-httpbis-p6-cache-05.txt
- I-D Action:draft-ietf-httpbis-p1-messaging-05.txt
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: Methods and Caching
- Re: #90: multipart/byteranges
- Re: Proposal for issue #101 (strong/weak validators).
- Re: NEW ISSUE: Methods and Caching
Sunday, 16 November 2008
- Re: NEW ISSUE: The role of Warning and Semantic Transparency in Caching
- Re: NEW ISSUE: Methods and Caching
Saturday, 15 November 2008
- Re: Status of issue #30 (Implied LWS)
- Re: NEW ISSUE: Methods and Caching
- Re: NEW ISSUE: The role of Warning and Semantic Transparency in Caching
- Re: Proposal for issue #101 (strong/weak validators).
- Re: #90: multipart/byteranges
- Re: Proposal for issue #101 (strong/weak validators).
- NEW ISSUE: Methods and Caching
- Re: #90: multipart/byteranges
- NEW ISSUE: The role of Warning and Semantic Transparency in Caching
- Re: Proposal for issue #101 (strong/weak validators).
Friday, 14 November 2008
- Re: Proposal for issue #101 (strong/weak validators).
- Re: Status of issue #30 (Implied LWS)
- Re: Status of issue #30 (Implied LWS)
- Re: Status of issue #30 (Implied LWS)
- Re: Status of issue #30 (Implied LWS)
- Re: Proposal for issue #101 (strong/weak validators).
- Re: Status of issue #30 (Implied LWS)
- Re: [new issue] Re: Proxying OPTIONS *
- Re: #90: multipart/byteranges
- Proposal for issue #101 (strong/weak validators).
- Re: #90: multipart/byteranges
- RE: #90: multipart/byteranges
- Re: Status of issue #30 (Implied LWS)
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- RE: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- RE: Status of issue #30 (Implied LWS)
- Re: Status of issue #30 (Implied LWS)
- Re: Status of issue #30 (Implied LWS)
- Re: estimated Content-Length with chunked encoding
- Re: Status of issue #30 (Implied LWS)
- Re: Status of issue #30 (Implied LWS)
- Re: [new issue] Re: Proxying OPTIONS *
- Re: [new issue] Re: Proxying OPTIONS *
- Re: [new issue] Re: Proxying OPTIONS *
- Re: [new issue] Re: Proxying OPTIONS *
- #90: multipart/byteranges
- Status of issue #30 (Implied LWS)
- PROPOSAL: #111 (Use of TEXT)
- Re: estimated Content-Length with chunked encoding
Tuesday, 11 November 2008
Sunday, 9 November 2008
- Re: Fwd: I-D Action:draft-pettersen-cookie-v2-03.txt
- Re: Fwd: I-D Action:draft-pettersen-cookie-v2-03.txt
- Re: Fwd: I-D Action:draft-pettersen-cookie-v2-03.txt
Thursday, 6 November 2008
Wednesday, 5 November 2008
Tuesday, 4 November 2008
- Re: proposed change for Issue 103 (content-*)
- RE: proposed change for Issue 103 (content-*)
- Re: Issue 133, was: multipart/byteranges minimum number of parts
- Re: proposed change for Issue 103 (content-*)
- Re: proposed change for Issue 103 (content-*)
- proposed change for Issue 103 (content-*)
Monday, 3 November 2008
- Fwd: I-D Action:draft-pettersen-cache-context-03.txt
- Fwd: I-D Action:draft-pettersen-cookie-v2-03.txt
- Fwd: I-D Action:draft-pettersen-dns-cookie-validate-04.txt
- Fwd: I-D Action:draft-pettersen-subtld-structure-04.txt
Saturday, 1 November 2008
Tuesday, 28 October 2008
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
Monday, 27 October 2008
- HTTP over SCTP draft submitted
- Re: estimated Content-Length with chunked encoding
- Re: server applying PUT to a resource other than the request-URI
Friday, 24 October 2008
Saturday, 25 October 2008
Friday, 24 October 2008
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- RE: server applying PUT to a resource other than the request-URI
- RE: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
Thursday, 23 October 2008
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
Wednesday, 22 October 2008
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
Tuesday, 21 October 2008
- New issue: redirected PUT, was: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- RE: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- RE: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
- Re: estimated Content-Length with chunked encoding
Monday, 20 October 2008
- Re: estimated Content-Length with chunked encoding
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: estimated Content-Length with chunked encoding
- Re: server applying PUT to a resource other than the request-URI
- estimated Content-Length with chunked encoding
- RE: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- RE: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- RE: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- RE: server applying PUT to a resource other than the request-URI
- Re: server applying PUT to a resource other than the request-URI
- RE: server applying PUT to a resource other than the request-URI
- server applying PUT to a resource other than the request-URI
Tuesday, 14 October 2008
Monday, 13 October 2008
- RE: Overlapping ranges
- Re: Overlapping ranges
- Re: must a partial response range be exact?
- RE: must a partial response range be exact?
Sunday, 12 October 2008
- Re: Overlapping ranges
- Re: must a partial response range be exact?
- RE: must a partial response range be exact?
- Re: must a partial response range be exact?
Saturday, 11 October 2008
Sunday, 12 October 2008
Saturday, 11 October 2008
- Re: must a partial response range be exact?
- Re: Overlapping ranges
- Re: must a partial response range be exact?
Friday, 10 October 2008
- RE: must a partial response range be exact?
- Re: must a partial response range be exact?
- Overlapping ranges
- Re: must a partial response range be exact?
Thursday, 9 October 2008
- Re: must a partial response range be exact?
- Re: must a partial response range be exact?
- Re: must a partial response range be exact?
- Re: Issue 133, was: multipart/byteranges minimum number of parts
Wednesday, 8 October 2008
- Re: must a partial response range be exact?
- Re: Issue 133, was: multipart/byteranges minimum number of parts
Monday, 6 October 2008
- OAuth authorization delegation protocol draft submitted
- Re: Issue 133, was: multipart/byteranges minimum number of parts
Friday, 3 October 2008
Thursday, 2 October 2008
- RE: iphone urls
- Re: iphone urls
- Re: must a partial response range be exact?
- Re: iphone urls
- Re: iphone urls
- Re: iphone urls
- iphone urls
- Re: [gears-eng] Re: [google-gears-eng] Re: Deploying new expectation-extensions
- Re: Status of Link header
- Re: (issue 100) - security considerations
- Re: minneapolis meeting plans
- Re: minneapolis meeting plans