[
https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444752#comment-13444752
]
Scott Wilson commented on WOOKIE-364:
-------------------------------------
The inbound configuration needs to be changed in a virtual host configuration
setup - e.g. when my server is really running at
http://internal.mydomain.org:8835/wookie but Apache is configured with a
virtual host of http://widgets.mydomain.org. In that case, when the connector
requests a widget, it gets an XML snippet including the URL to use for
rendering; that needs to use the virtual host domain, not the real (internal)
domain, as the "real" URL is not externally visible.
> Wookie delegates proxy settings to widgets
> ------------------------------------------
>
> Key: WOOKIE-364
> URL: https://issues.apache.org/jira/browse/WOOKIE-364
> Project: Wookie
> Issue Type: Bug
> Components: Connection Framework
> Affects Versions: 0.12.0, 0.13.0
> Environment: Windows7 x64, Java7 x32, corporate firewall & proxy
> Reporter: Matthias Niederhausen
> Labels: proxy
> Fix For: 0.13.0
>
> Attachments: patch.txt
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When I set proxy settings in the widgetserver.properties file to use my
> corporate proxy, Wookie will not only use these settings for its internal
> ProxyClient, but also relay these settings to the client-side widgets, which
> then try to directly connect to my corporate proxy. Of course, due to
> cross-domain-access policies, this will fail and it also circumvents the
> Wookie proxy security.
--
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
