[
https://issues.apache.org/jira/browse/WOOKIE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628769#comment-13628769
]
Scott Wilson commented on WOOKIE-411:
-------------------------------------
Yep, I think also it would be good to be able to just configure this once for
the whole setup, rather than separately configure Rave, Shindig and Wookie. One
possibility is to check global environment variables as well as the local
configuration - see WOOKIE-361 for a discussion of that.
> Wookie can not be deployed behind a reverse proxy
> -------------------------------------------------
>
> Key: WOOKIE-411
> URL: https://issues.apache.org/jira/browse/WOOKIE-411
> Project: Wookie
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.14.0
> Environment: Windows Server 7 x64
> Reporter: Matthias Niederhausen
>
> When I try to deploy Wookie with Rave behind a reverse proxy, I can't get it
> to work.
> When serving a widget, Wookie somehow seems to grab the internal URL to
> return a widget URL, which can not be resolved by the client.
> In our setting, we have Rave and Wookie running under port 8080, which is
> exposed as port 80 to the public (trying to get Rave and Wookie running under
> port 80 directly failed miserably). When I load a workspace, the widgets try
> to get the files from
> http://omelette.eu:8080/wookie/deploy...&proxy=http://omelette.eu:8080/wookie/proxy&st=,
> which is not publicly available.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
