httpbis: Ticket #50: Misc. Typos
Link: http://trac.tools.ietf.org/wg/httpbis/trac/ticket/50
Origin:
http://www.w3.org/mid/86EDC3963F04D546BED8996F77D290F6049C895F63@NA-EXMSG-C138.redmond.corp.microsoft.com
Component:
non-specific
- Section 7.1, page 42: Some of this metainformation is "OPTIONAL"; some might be "REQUIRED" by portions of this specification.
- Section 13.13, page 99: Even though sometimes such resources ought not
to
be cached, or ought to expire quickly, user interface considerations may force service authors to resort to other means of preventing caching (e.g. "once-only" URLs) in order not to suffer the effects of improperly functioning history mechanisms.
- Section 14.18, page 124: The field value is an HTTP-date, as described in section 3.3.1; it MUST be sent in the RFC 1123 [8]
-
date format.
- Section 14.23, page 129: A client MUST include a Host header field in all HTTP/1.1 request messages
.
- Section 14.32, page 137: Note: because the meaning of "Pragma: no-cache" as a response
-header field is not actually specified, it does not provide a reliable replacement for "Cache-Control: no-cache" in a response.
- Section 15.6, page 155: HTTP/1.1
. does not provide a method for a server to direct clients to discard these cached credentials.
- Section 2.1, page 15: At least one delimiter (LWS and/or
separators) MUST exist between any two tokens (for the definition of "token" below), since they would otherwise be interpreted as a single token.
Mails
Associated Checkins
- fielding@gbiv.com
(Sat, 05 Jan 2008 02:43:56 GMT)
-
[148]:
Fix remaining Misc. Typos to address #50.
-
[144]:
Fix typo (ought not to cached)
-
[83]:
Resolve #48: Date reference typo
-
[100]:
Second part of resolution for #48: Date reference typo
-
[148]:
Fix remaining Misc. Typos to address #50.
-
[148]:
Fix remaining Misc. Typos to address #50.
-
[145]:
Fix typo ("HTTP/1.1.")
History
: comment added; component, milestone set (Fri, 04 Jan 2008 06:11:06 GMT)
-
component
set to non-specific
-
milestone
set to unassigned
: comment added; resolution set; status, milestone changed (Sat, 05 Jan 2008 02:43:56 GMT)
-
status
changed from new to closed.
-
resolution
set to fixed
-
milestone
changed from unassigned to 01.
As numbered above ...
1. this sentence is meaningless and has been removed in [148].
2. fixed in [144].
3. see ticket #48. fixed in [83] and [100].
4. fixed in [148].
5. fixed in [148].
6. fixed in [145].
7. fixed when converted to XML.
Related Information
Issues List Index