[
https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444058#comment-13444058
]
Scott Wilson commented on WOOKIE-364:
-------------------------------------
Thanks for the patch Matthias,
I just want to understand the context of this a little better as I'm not sure
what the best solution is. I'm assuming by corporate proxy you mean a
forwarding proxy that affects outbound requests from within your network?
I think what is happening here is a conflict between the the inbound
configuration (the URL widgets need to use to invoke the Wookie server-side
proxy) and the outbound configuration (the settings applied to HttpClient when
the Wookie proxy makes a request on behalf of the widget). Usually these are
the same, but in your case it would appear that they need to be different and
would need additional configuration - I think this would need a very careful
explanation of what the settings affect as it would be quite easy to make a
mistake.
Maybe:
##
## Settings used for determining the proxy URL to be used
## by widgets. The default is to use the Wookie whitelist proxy
## using the inbound request scheme, host and port mapped to /proxy
##
widget.proxy.scheme=
widget.proxy.hostname=
widget.proxy.port=
widget.proxy.path=/proxy
(this is used to setup the URL passed back to WidgetInstances)
##
## Where a system forwarding proxy is in place for your network, use
## the settings below to configure the internal proxy host and port. This
## information is used in the internal HttpClient configuration and is not
## exposed externally.
##
system.proxy.hostname=
system.proxy.port=
(this is only used by ConnectionsPrefsManager.setProxySettings)
> 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
