[jira] [Comment Edited] (WOOKIE-411) Wookie can not be deployed behind a reverse proxy

["Matthias Niederhausen (JIRA)" <ji...@apache.org>]

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

Matthias Niederhausen edited comment on WOOKIE-411 at 4/8/13 8:21 AM:
----------------------------------------------------------------------

Duh, overlooked this. Now I feel dumb.
But it works! =)
                
      was (Author: javafrog):
    Duh, overlooked this. Now I feel dumb.
                  
> 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