Closed artegz closed 9 years ago
Related issue at Resin bug tracker - http://bugs.caucho.com/view.php?id=5830
@jfarcand this is causing Jetty 4 v20170914 to explode under Chrome. Jetty is allowing two headers - an Upgrade: "" and Upgrade: "WebSocket" (and Server: "" and Server: "Jetty v....") which is making Chrome fail because of two headers.
Jetty expects this to be passed as null (thus unsetting it). I have had to add a response delegate to remove the header. It appears to be a Jetty bug.
I'm trying to run atmosphere framework within Resin 4 application server but has encountered some problems. I've build atmosphere-chat war from sample sources and deployed it. When I've opened it in browser following exception has been occurred.
Looks like it failed while using fallback long-polling transport. I'he also tried this example with other transports and other examples (atmosphere-chat-sse, atmosphere-ee6) but without success - exception disappeared but messages not came. I've tried to run same examples within glassfish and everything works fine.
Related google groups topic (https://groups.google.com/forum/#!topic/atmosphere-framework/dA2JVfGZFic).
Sample atmosphere-chat uses atmosphere framework 2.3.0-SNAPSHOT version, but problem also reproduces with 2.2.3 version. Resin version - 4.0.41
Log: