"Connection" header field value must start with upper case letter

[harendt]

According to https://datatracker.ietf.org/doc/html/rfc6455#section-4.1, Page 18, the Connection header field MUST include the "Upgrade" token. But Beast uses a lower case "upgrade" token instead.

There are several occurrences., for example:

• https://github.com/boostorg/beast/blob/710cc53331f197f6f17e8c38454c09df68e43c03/include/boost/beast/websocket/impl/stream_impl.hpp#L632
• There are several occurrences. For example: https://github.com/boostorg/beast/blob/710cc53331f197f6f17e8c38454c09df68e43c03/include/boost/beast/websocket/impl/rfc6455.hpp#L29

[madmongo1]

However: https://datatracker.ietf.org/doc/html/rfc2616#section-4.2

Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive.

[harendt]

The "Upgrade" token is a field value, not a field name. Don't know what that RFC says about case sensitivity of field values ...

[vinniefalco]

Don't know what that RFC says about case sensitivity of field values

They are case-insensitive unless otherwise specified.

https://datatracker.ietf.org/doc/html/rfc2616#section-2.1

[stale[bot]]

This issue has been open for a while with no activity, has it been resolved?

[klemens-morgenstern]

Beast follows the standard here, so unless you've got a use-case that requires case-sensitivity, I'd like to close this issue.