Ticket #366 (closed editorial: incorporated)
Conditional Requests editorial suggestions
|Reported by:||email@example.com||Owned by:||firstname.lastname@example.org|
|Component:||p4-conditional||Severity:||In WG Last Call|
- - section 1, p3, Introduction, first sentence
I can not parse that sentence, should it perhaps be "....on that metadata be checked...." -> "....on that metadata; to be checked...."?
- - 1.1, p3, conformance and error handling, 3d paragraph
I don't get the statement about "SHOULD-level" requirements. Isn't that always the case with SHOULD? I.e. what is different from RFC2119?
- - 1.2, p4, Syntax
I think it would be helpful to state what OWS, obs-text and HTTP-date (informal) stand for, the production rule given here does not provide much clarity
- - 2.2, p6 last-modiefied
This paragraph came a bit out of the blue it is not mentioned that Last-Modified is one of the validators that you just talked about in the previous paragraph
- - 2.2.1, p7, generation, one but last paragraph
Seems that a bad system clock can nevertheless screw things up, if the system clock is set to earlier than the previous "fresh page" the content will never be updated.
- - 2.3 ETag, p9, 2nd paragraph
The "more reliable" and "convenient" don't seem to be related, even though that is suggested in the paragraph. I would argue that an entity-tag can be implemented to be more reliable period (because of the clock problems discussed before)
- - 2.4, p12, Rules.... HTTP/1.1 clients
So if I understand the "MUST use the entity-tag" correctly the heuristic that is being used for servers can not be used here. Like in the server example I could imagine that also the client could decide not to fetch new weather data based on some internal rule (because it is mobile and wants to avoid rapid updates for example)
The MAY use the Last-Modified in the case of an HTTP/1.0 origin server deserves some explanation, not being an HTTP expert it is unclear to me what makes it deifferent for 1.1
3.1, p 13, If-Match
Most HTTP return codes are expanded, highly appreciated! Could you please do that for all, i.e. "304" -> "304 (not modified)" etc., that makjes for a much easier read.
3.3, p16 If-Modified-Since, First Note:
What is the consequence of the Range header field modifying the meaning?
- Origin set to http://www.ietf.org/mail-archive/web/secdir/current/msg03268.html