Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Clarify response header capitalisation
We don't actually REQUIRE lowercase, it's just a nice convention to have. Some rare clients do, actually, care about case, so carve out a best-effort channel for that.
- Loading branch information
c1d3d97
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@andrewgodwin there are other places "Header names must be lowercased." appear in this document. Should they also be changed like you did for this first instance?
c1d3d97
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, I forgot that was all duplicated in the second section. Fixed.
c1d3d97
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there some background on this change?
I'm don't have a "for-or-against" but it'd be helpful to understand the intent, since "Header names should be lowercased [...] servers should preserve header case" is a bit ambiguous to me.
c1d3d97
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have opened an issue on this for further discussion: #246