Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] jetty-9.1.4 : some websocket header names are not case-insensitive

The header name map should be case-insensitive.

Opened a bug for it

Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Tue, Apr 29, 2014 at 9:25 AM, MILLON, YVES (YVES) <yves.millon@xxxxxxxxxxxxxxxxxx> wrote:
When we try to negociate subprotocol with a custom ServerEndpointConfig.Configurator, we got an empty list of requested subprotocols if the header name does not match exactly "Sec-WebSocket-Protocol" (in our case, the client adds the header " Sec-Websocket-Protocol").
This is not compliant with RFC2616 4.2 and it seems that it is located in the class ServletUpdateRequest delaing with subprotocols and extensions.

jetty-users mailing list

Back to the top