You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Matthias Niederhausen (JIRA)" <ji...@apache.org> on 2012/08/23 09:49:41 UTC
[jira] [Created] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Matthias Niederhausen created WOOKIE-364:
--------------------------------------------
Summary: 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
Fix For: 0.13.0
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Matthias Niederhausen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444744#comment-13444744 ]
Matthias Niederhausen commented on WOOKIE-364:
----------------------------------------------
I think you grasped it quite right. The corporate proxy does indeed affect all outbound requests from our network. An application can not access any web resource without using the proxy.
What I do not understand is under which circumstances the inbound configuration needs to be changed. When the browser requests a widget from the server, it must already have the right configuration, otherwise it could not download the widget in the first place. When the widget is then executed and requests some service, must it not connect to the very same server, where Wookie resides? So I don't see that this configuration ever needs to be done.
Aside from that, I think the solution you propose would be viable to solve the problem.
> 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
[jira] [Commented] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444775#comment-13444775 ]
Scott Wilson commented on WOOKIE-364:
-------------------------------------
Do you want to give it a try and see if it works for you?
> 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
[jira] [Updated] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Matthias Niederhausen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Niederhausen updated WOOKIE-364:
-----------------------------------------
Attachment: patch.txt
The new patch introduces system.proxy settings.
Also, widget.proxy.username, widget.proxy.password and widget.proxy.usentlmauthentication were renamed to be in line, as they were only used by the ConnectionPrefsManager.
> 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, 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
[jira] [Updated] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Matthias Niederhausen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Niederhausen updated WOOKIE-364:
-----------------------------------------
Attachment: patch.txt
This patch disables the WidgetInstancesController from forwarding the internal proxy settings to the client-side widgets.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Matthias Niederhausen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444786#comment-13444786 ]
Matthias Niederhausen commented on WOOKIE-364:
----------------------------------------------
Okay, so I submit another patch that introduces a new system.proxy setting?
> 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
[jira] [Commented] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444934#comment-13444934 ]
Scott Wilson commented on WOOKIE-364:
-------------------------------------
yes please!
> 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
[jira] [Commented] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Matthias Niederhausen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WOOKIE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444754#comment-13444754 ]
Matthias Niederhausen commented on WOOKIE-364:
----------------------------------------------
Ah okay, thanks for clarifying =)
So best to use two distinguished settings, then.
> 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
[jira] [Commented] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (WOOKIE-364) Wookie delegates proxy settings to
widgets
Posted by "Scott Wilson (JIRA)" <ji...@apache.org>.
[ 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