"If a port is not provided, a recipient MAY interpret that as meaning it was
received on the default TCP port, if any, for the received-protocol."
So if received-protocol is "3", it's a UDP port.
If received-protocol is "1" or "1.1", is the default port 80 or 443? IIUC the
scheme isn't included to determine this.
Editors: #881
"A proxy that transforms the content of a 200 (OK) response can inform
downstream recipients that a transformation has been applied by changing the
response status code to 203 (Non-Authoritative Information)"
Why not an normative word, instead of "can"?
Editors: #857 (comment)
Editors: #857 (comment)
Why not s/ought to/SHOULD ?
Editors: #857 (comment)
Editors: #882
Editors: #883
Editors: #857 (comment)
Editors: #890
Editors: #884
Editors: see #886 and #885
"If a port is not provided, a recipient MAY interpret that as meaning it was
received on the default TCP port, if any, for the received-protocol."
So if received-protocol is "3", it's a UDP port.
If received-protocol is "1" or "1.1", is the default port 80 or 443? IIUC the
scheme isn't included to determine this.
Editors: #881
"A proxy that transforms the content of a 200 (OK) response can inform
downstream recipients that a transformation has been applied by changing the
response status code to 203 (Non-Authoritative Information)"
Why not an normative word, instead of "can"?
Editors: #857 (comment)
Accept-Encoding are synonymous?
Editors: #857 (comment)
respond with a 415 (Unsupported Media Type) status"
Why not s/ought to/SHOULD ?
Editors: #857 (comment)
intermediaries?
Editors: #882
field"... (13.1.5) leads me to believe that only clients can send If-Range. So
how can there be a response with If-Range?
Editors: #883
this is intentional, it ought to be explained.
Editors: #857 (comment)
SHOULD begin with "an alphanumeric character". More broadly, the "Field name:"
description in (16.3.1) should probably refer to (16.3.2.1) unless I'm
misunderstanding the scope of these sections.
Editors: #890
Editors: #884
(12.5.1), and accept-charset is deprecated in (12.5.2), if that is new to this
spec.
Editors: see #886 and #885