You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Scott Wilson (JIRA)" <ji...@apache.org> on 2010/10/07 20:56:30 UTC

[jira] Updated: (WOOKIE-111) Enable support for virtual hosts

     [ https://issues.apache.org/jira/browse/WOOKIE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Scott Wilson updated WOOKIE-111:
--------------------------------

    Fix Version/s:     (was: 0.8.1)
                   0.8.2

Noted issue in the readme; to fix in next release

> Enable support for virtual hosts
> --------------------------------
>
>                 Key: WOOKIE-111
>                 URL: https://issues.apache.org/jira/browse/WOOKIE-111
>             Project: Wookie
>          Issue Type: Improvement
>          Components: Configuration, Server
>            Reporter: Scott Wilson
>             Fix For: 0.8.2
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> 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!)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.