java.lang.IllegalStateException: !HTTP/1.1

[PS]

I observe following error in cometd 2.5.1. Is this related to some browser incorrectly upgrading to websocket or is there a problem in cometd?

java.lang.IllegalStateException: !HTTP/1.1

        at org.eclipse.jetty.websocket.WebSocketFactory.upgrade(WebSocketFactory.java:205)

        at org.eclipse.jetty.websocket.WebSocketFactory.acceptWebSocket(WebSocketFactory.java:351)

        at org.cometd.websocket.server.WebSocketTransport.handle(WebSocketTransport.java:157)

        at org.cometd.server.CometdServlet.service(CometdServlet.java:166)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)

        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1329)

        at org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:247)

        at org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:210)

        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)

        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)

        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)

        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:559)

        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)

        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)

        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:374)

        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)

        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:972)

        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)

        at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255)

        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)

        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)

        at org.eclipse.jetty.server.Server.handle(Server.java:363)

        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483)

        at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:920)

        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:982)

        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635)

        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)

        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)

        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)

        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)

        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)

        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)

        at java.lang.Thread.run(Thread.java:722)

[Simone Bordet]

Hi,

On Sat, Apr 20, 2013 at 11:02 PM, PS <peter...@gmail.com> wrote:
> I observe following error in cometd 2.5.1. Is this related to some browser
> incorrectly upgrading to websocket or is there a problem in cometd?
>
> java.lang.IllegalStateException: !HTTP/1.1

The client sent a HTTP 1.0 request, which is invalid when trying to
upgrade to WebSocket.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.

[PS]

Does cometd automatically falls back to use long-polling in this case?

[Simone Bordet]

Hi,

On Sat, May 11, 2013 at 9:28 PM, PS <peter...@gmail.com> wrote:
> Does cometd automatically falls back to use long-polling in this case?

Yes.

[PS]

On this error in log:

2013-05-13 10:29:09.165:WARN:oejw.WebSocketFactory:Unsupported websocket client version specification <Unspecified, likely a pre-draft version of websocket>, configured minVersion [13], reported supported versions [13]

1. does cometd also falls back to long-polling automatically?

2. which websocket version is required (so I can find which browsers implement it and alert my users to use those  browsers)?

[PS]

I expected something in that sense (I am using Jetty 7.6.10 at the moment as that is default/recommended by cometd 2.6.0), but my main concern is if cometd automatically falls back to long-polling for such clients.

(Because I see many of these printouts in the log file, there is quite large population that uses browsers with pre 13 websocket version, I just want to make sure my app works for such users)

[PS]

when I see

2013-05-18 13:09:19.288:WARN:oejw.WebSocketFactory:Unsupported websocket client version specification <Unspecified, likely a pre-draft version of websocket>, configured minVersion [13], reported supported versions [13]

2013-05-18 13:09:21.991:WARN:oejw.WebSocketFactory:Unsupported websocket client version specification <Unspecified, likely a pre-draft version of websocket>, configured minVersion [13], reported supported versions [13]

2013-05-18 13:09:28.078:WARN:oejw.WebSocketFactory:Unsupported websocket client version specification <Unspecified, likely a pre-draft version of websocket>, configured minVersion [13], reported supported versions [13]

...

this is from single client connection (like 25 rows of same error), why do I see so many logs for this, instead of just one? This is why I am concerned that cometd does not switch to long-polling in this scenario. Does it?