[
https://issues.apache.org/jira/browse/WOOKIE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051730#comment-13051730
]
Scott Wilson commented on WOOKIE-111:
-------------------------------------
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.
> 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
> Labels: configuration, virtual_hosts
> Fix For: 0.9.1
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
