Details

      Description

      When Wookie is deployed using a virtual host configuration, it still sends instance URLs that use the real server location.

      E.g. if Wookie is deployed at "bernard.myco.com:8080/wookie" but is served from the virtual host "services.myco.com/wookie" requests to the REST API to instantiate a widget returns a URL starting "bernard.myco.com:8080".

      It should be possible to specify a vhost server name in configuration to override this behaviour.

      NB There may be other functions in Wookie that would also need to be aware of any vhost settings.

      (Originally suggested by David Sherlock - thanks David!)

        Activity

        Paul Sharples made changes -
        Status Closed [ 6 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Paul Sharples added a comment -

        Verified. Changing the values allow the instance urls to point to new location. Also flatpacks now contain the path to the specified url, rather then the default. Documentation found here: http://incubator.apache.org/wookie/docs/developer/running.html

        Show
        Paul Sharples added a comment - Verified. Changing the values allow the instance urls to point to new location. Also flatpacks now contain the path to the specified url, rather then the default. Documentation found here: http://incubator.apache.org/wookie/docs/developer/running.html
        Scott Wilson made changes -
        Status Open [ 1 ] Closed [ 6 ]
        Hide
        Scott Wilson added a comment -

        Implemented a fix for this, but it needs testing.

        Show
        Scott Wilson added a comment - Implemented a fix for this, but it needs testing.
        Hide
        Scott Wilson added a comment -

        As a first step we need a single class within Wookie where the current host, port and servlet context are accessed, which can be overridden by property settings where necessary. There are quite a few places within Wookie where we get this information dynamically (e.g. request.getSession().getServletContext()) which we would have to replace.

        Show
        Scott Wilson added a comment - As a first step we need a single class within Wookie where the current host, port and servlet context are accessed, which can be overridden by property settings where necessary. There are quite a few places within Wookie where we get this information dynamically (e.g. request.getSession().getServletContext()) which we would have to replace.
        Ross Gardler made changes -
        Fix Version/s 0.9.1 [ 12315418 ]
        Fix Version/s 0.8.2 [ 12314217 ]
        Scott Wilson made changes -
        Fix Version/s 0.8.2 [ 12314217 ]
        Fix Version/s 0.8.1 [ 12314216 ]
        Hide
        Scott Wilson added a comment -

        Noted issue in the readme; to fix in next release

        Show
        Scott Wilson added a comment - Noted issue in the readme; to fix in next release
        Ross Gardler made changes -
        Field Original Value New Value
        Status Ready To Review [ 10006 ] Open [ 1 ]
        Scott Wilson created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Scott Wilson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2h
              2h
              Remaining:
              Remaining Estimate - 2h
              2h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development