WebSocket support on Jetty always uses SockJS HTTP fallbacks [SPR-10861]

[spring-projects-issues]

Scott Andrews opened SPR-10861 and commented

Creating a SockJS connection to a Jetty application running on localhost ends up using the HTTP fallbacks instead of a native WebSocket.

This was seen running on 4.0.0.BUILD-SNAPSHOT. As recently as a few days ago, native a WebSocket was being used.

There are no errors in the log, but this statement may be of interest:

15:56:32 [qtp652713850-31] DefaultSockJsService - GET with SockJS path [/754/2eu5deed/websocket]
15:56:32 [qtp652713850-31] DefaultSockJsService - Transport handler not found

From the client, the attempt to open a WebSocket results in a 404.

---

Affects: 4.0 M2

Referenced from: commits c48a41e