[
https://issues.apache.org/jira/browse/WICKET-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886451#comment-13886451
]
Martin Grigorov commented on WICKET-5453:
-----------------------------------------
Reworked JSR356 integration to be based on ServerApplicationConfig and tested
it with Tomcat 8.0.1 and Jetty 9.1.1.
This overcome the previous problem with Glassfish but then I hit two new bugs
so it still doesn't work ..
Additionally tested the problem with Sec-WebSocket-Protocol with Chrome 32
(there was a fix required in Tomcat 8.0.0, thus 8.0.1). Works fine with Jetty
9.0.7 and 9.1.1.
There returned error code for Sec-WebSocket-Version is changed to 400 as
suggested.
I didn't work on the problems with Sec-WebSocket-Draft because I have no
iWidgets around.
So the only thing that left here is the configurability problem. Looking at
Jetty's sources I think it is possible to do something like:
WebSocketServerContainerInitializer.configureContext(webAppContext);
WebSocketUpgradeFilter upgradeFilter =
(WebSocketUpgradeFilter)
webAppContext.getAttribute(WebSocketUpgradeFilter.class.getName());
upgradeFilter.getFactory().getPolicy().setIdleTimeout(5000);
before starting the Server instance.
[~joakime] Is this OK
> Jetty 9.1.0 has its own UpgradeFilter, use it
> ---------------------------------------------
>
> Key: WICKET-5453
> URL: https://issues.apache.org/jira/browse/WICKET-5453
> Project: Wicket
> Issue Type: Bug
> Components: wicket-native-websocket
> Affects Versions: 7.0.0
> Reporter: Joakim Erdfelt
> Assignee: Martin Grigorov
> Priority: Minor
>
> In a recent stackoverflow question ..
> http://stackoverflow.com/questions/20661139/websocket-timeout-with-apache-wicket-and-embedded-jetty
> I noticed a reference to a class called Jetty9WebSocketFilter
> Starting in Jetty 9.1.0, a filter for websocket upgrade ships with Jetty.
> See answer (with example code):
> http://stackoverflow.com/a/20663447/775715
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
