[jetty-users] jetty-9.1.4 : some websocket header names are not case-ins

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jetty-users] jetty-9.1.4 : some websocket header names are not case-insensitive

From: "MILLON, YVES (YVES)" <yves.millon@xxxxxxxxxxxxxxxxxx>
Date: Tue, 29 Apr 2014 16:25:15 +0000
Accept-language: fr-FR, en-US
Delivered-to: jetty-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jetty-users>
List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>
Thread-index: Ac9jx5oOy+Kd/oVZRjaMPwTCUx3euw==
Thread-topic: jetty-9.1.4 : some websocket header names are not case-insensitive

Hi,

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.

Regards,

Yves

Follow-Ups:
- Re: [jetty-users] jetty-9.1.4 : some websocket header names are not case-insensitive
  - From: Joakim Erdfelt

Prev by Date: Re: [jetty-users] Jetty-9.1.4 : NPE in Log.java
Next by Date: Re: [jetty-users] jetty-9.1.4 : some websocket header names are not case-insensitive
Previous by thread: [jetty-users] WebAppClassLoader.addClassPath() throws IllegalArgumentException: !file
Next by thread: Re: [jetty-users] jetty-9.1.4 : some websocket header names are not case-insensitive
Index(es):
- Date
- Thread

Breadcrumbs