Uploaded image for project: 'Wookie'
  1. Wookie
  2. WOOKIE-411

Wookie can not be deployed behind a reverse proxy

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 0.14.0
    • Fix Version/s: None
    • Component/s: Server
    • Labels:
      None
    • Environment:
      Windows Server 7 x64

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              javafrog Matthias Niederhausen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: