You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/10/15 08:55:21 UTC

[jira] [Commented] (WICKET-6254) Wicket WebSockets problem behind HTTP proxy without servlet context

    [ https://issues.apache.org/jira/browse/WICKET-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15577700#comment-15577700 ] 

ASF subversion and git services commented on WICKET-6254:
---------------------------------------------------------

Commit 41a3b04a57a731e5723493092bce748aca58588c in wicket's branch refs/heads/wicket-7.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=41a3b04 ]

WICKET-6254 Wicket WebSockets problem behind HTTP proxy without servlet context

Make it possible to override the parts needed to construct the WebSocket absolute url.
This is needed when the application runs in a servlet container that is proxied in front.
The constructed url has to point to the proxy server.
The application may use X-Forwarded-For-** headers set by the proxy, or custom configuration for different environments


> Wicket WebSockets problem behind HTTP proxy without servlet context
> -------------------------------------------------------------------
>
>                 Key: WICKET-6254
>                 URL: https://issues.apache.org/jira/browse/WICKET-6254
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-native-websocket
>    Affects Versions: 7.3.0
>            Reporter: Tom Götz
>            Assignee: Martin Grigorov
>
> See discussion here:
> http://apache-wicket.1842946.n4.nabble.com/Wicket-WebSockets-problem-with-servlet-context-td4675647.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)