Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#441 closed editorial (incorporated)

P1 editorial nits

Reported by: julian.reschke@… Owned by: draft-ietf-httpbis-p1-messaging@…
Priority: normal Milestone: 23
Component: p1-messaging Severity: In WG Last Call
Keywords: Cc:

Description (last modified by fielding@…)

Sec 2.6, last para, last sentence: "avoiding" -> "avoided"

Sec 3.1.1, para 5: "No whitespace is allowed inside the method, request-target, and protocol version." I think "or" would read better than "and".

Sec 4.1.2: The ABNF states that all chunks (including last-chunk) may include chunk-ext, so the last line of the first while() loop should be:

read chunk-size, chunk-ext (if any) and CRLF

Sec 6.6, second last para: The first sentence is quite long and it took me several reads to parse it correctly. I'd suggest adding a comma to separate the two ways that the server can receive an ack of the close from the client, e.g.: "... until the connection is closed by the client, or the server is reasonably certain ..."

Sec A.1.2, last para: "need will need" -> "need" or "will need"

Change History (4)

comment:1 Changed 6 years ago by julian.reschke@…

From [2214]:

editorial fixes (see #441)

comment:2 Changed 6 years ago by julian.reschke@…

  • Description modified (diff)

comment:3 Changed 6 years ago by fielding@…

  • Description modified (diff)
  • Resolution set to incorporated
  • Status changed from new to closed

From [2257]:

(editorial) #441: clarify handling of whitspace in request-line; clarify how a server initiates a close and remove the Apache-ism of "lingering close" that might be confused with SO_LINGER; fix the pseudo-code example explaining chunk parsing

comment:4 Changed 6 years ago by julian.reschke@…

From [2315]:

record change (see #441)

Note: See TracTickets for help on using tickets.