NEW: value space of status codes [#213]
preparing new drafts for IETF 78
FW: I-D Submission: draft-lee-httpext-metadata-00.txt
clarity needed for browser behaviors when receiving 206 status codes
- Re: clarity needed for browser behaviors when receiving 206 status codes
- Re: clarity needed for browser behaviors when receiving 206 status codes
Fwd: HTTPBIS - Requested session has been scheduled for IETF 78
[CSAIL #48734] AutoReply: Message received
[CSAIL #48586] AutoReply: Re: Message received
semantic equivalence of delimiters in URIs
'Age' for web pages
Managing multiple authorities, resources and representations
IETF BoF @IETF-78 Maastricht: HASMAT - HTTP Application Security Minus Authentication and Transport
Fwd: I-D Action:draft-loreto-http-timeout-00.txt
- Re: Fwd: I-D Action:draft-loreto-http-timeout-00.txt
Handling multiple headers when only one is allowed
- Re: Handling multiple headers when only one is allowed
- Re: Handling multiple headers when only one is allowed
- Re: Handling multiple headers when only one is allowed
- "actual content length", was: Handling multiple headers when only one is allowed
Fwd: I-D Action:draft-ietf-core-coap-00.txt
Revisiting Retry-After w/ 202
HTTP Application Security (HAS) BoF
#122 (MIME-Version not listed in P1, general header fields)
#168: understanding CC directives
Re: Questions (errata?) about caching authenticated responses [#174]
- Re: Questions (errata?) about caching authenticated responses [#174]
- Re: Questions (errata?) about caching authenticated responses [#174]
Broken link
Duplicating request component in an HTTP authentication scheme
- Re: Duplicating request component in an HTTP authentication scheme
- Re: Duplicating request component in an HTTP authentication scheme
short-time client side caching and clock skew
http progress notification
update: http progress notification
- Re: update: http progress notification
Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
- Re: Issue 163, was: Meaning of invalid but well-formed dates
Same resource exposed over HTTP and HTTPS
- Re: Same resource exposed over HTTP and HTTPS
Query string cacheability
- Re: Query string cacheability
- Re: Query string cacheability
Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
- Re: TAG requests addition to section 3.2.1 of Part 3 [#155]
304 updating ETag
Missing specification in RFC 2617, cannot use a user name nor a password in encoding different from ISO-8859-1
Re: FYI Cache-control deployment
RE: Multiple challenges in a single WWW-Authenticate header field
Re: Cache behavior for authenticated contents
Re: Expect: 100-continue and proxies
- Re: Expect: 100-continue and proxies
- Re: Expect: 100-continue and proxies
- Re: Expect: 100-continue and proxies
Re: one time passwords from private keys
Re: What are "appropriate Cache-Control or Expires header fields"
RE: What are "appropriate Cache-Control or Expires header fields"
Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
- Re: Concurrent non-error response disallowed. ("clarification of 7.2.2. Monitoring Connections for Error Status Messages")
Clarification on use of Content-Location header
Fwd: [http-state] WG Last Call for draft-ietf-httpstate-cookie-08 ?
Re: 300 Multiple Choices and safe methods
Re: proposal for issue #178
- Re: proposal for issue #178
Re: proposal for issue #175 range flooding
Re: 3 short questions, Entity Tag & Content Location
ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content
- Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content
- Re: ticket 208, Re: RFC 5861 on HTTP Cache-Control Extensions for Stale Content
Fwd: RFC 5861 on HTTP Cache-Control Extensions for Stale Content
Revitalizing Caching ✩ Mozilla Hacks – the Web developer blog
Re: [http-state] Missing specification in RFC 2617, cannot use a user name nor a password in encoding different from ISO-8859-1
In support of sending fragment IDs to the server (issue #43)
Re: Protocol Action: 'Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters' to Proposed Standard
Labs/Weave/Identity/Account Manager/Spec/Latest - MozillaWiki
Re: I-D Action:draft-reschke-rfc2231-in-http-12.txt
is rfc2616 the right document to study
Explicit instructions on use of fragment in request URI
- Re: Explicit instructions on use of fragment in request URI
- Re: Explicit instructions on use of fragment in request URI
clarification of 7.2.2. Monitoring Connections for Error Status Messages
- Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages
- Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages
- Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages
- Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages
- Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages
- Re: clarification of 7.2.2. Monitoring Connections for Error Status Messages
Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- RE: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
- Re: Issue 196, was: #110: how to determine what entity a response carries
Issue 200 ("word" in ABNF), was: suggestions for examples and explication wrt ABNF and header fields in draft-ietf-httpbis-p1
Transfer-Encoding in a HEAD response
How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)
- Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)
- Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)
- Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)
- Re: How many coding registries should we have? (Issue 143), was: Issue 189, Re: Content/Transfer-Codings organization/IANA considerations (issue 143, 188, 189)
pack200-gzip Content Coding
Ticket 183: "requested resource" in content-encoding definition
Age response header and HTTP/1.0 requests
Fwd: I-D Action:draft-nottingham-http-link-header-09.txt
Re: Issue 165, was: Issue 163, was: Meaning of invalid but well-formed dates
Re: #73: httpbis and deflate compression...
Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Issue 101, was: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg
- Re: Issue 39: proposed example for varying the etag based on conneg