You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Option names are just human readable labels assigned to numeric options; there is no need to normalize them because they never show up on the wire. For what it's worth, those could even be renamed (looking at you, Referer).
I trust that the designated experts who review the addition of options will reject options whose name is already present in different capitalization or spelling.
(I think this issue can be closed, there is nothing actionable for this site).
I'm curious if option names are case-sensitive? In RFC2616, section 4.2 Message Headers, the header names are deemed case-insensitive.
I did not see case-sensitivity mentioned in RFC7252.
Was this an oversight? Is there some way to propose its inclusion, or is it too late for that?
linking relevant issue: coapjs/node-coap#71
The text was updated successfully, but these errors were encountered: