Opened 12 years ago

Closed 12 years ago

#50 closed editorial (fixed)

Misc. Typos

Reported by: mnot@… Owned by:
Priority: Milestone: 01
Component: non-specific Severity:
Keywords: Cc:

Description

  1. Section 7.1, page 42: Some of this metainformation is "OPTIONAL"; some might be "REQUIRED" by portions of this specification.
  2. Section 13.13, page 99: Even though sometimes such resources ought not tobe 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.
  3. 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.
  4. Section 14.23, page 129: A client MUST include a Host header field in all HTTP/1.1 request messages .
  5. 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.
  6. Section 15.6, page 155: HTTP/1.1. does not provide a method for a server to direct clients to discard these cached credentials.
  7. 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.

Change History (2)

comment:1 Changed 12 years ago by mnot@…

  • Component set to non-specific
  • Milestone set to unassigned

comment:2 Changed 12 years ago by fielding@…

  • Milestone changed from unassigned to 01
  • Resolution set to fixed
  • Status changed from new to closed

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.
Note: See TracTickets for help on using tickets.