Today I am working at a client site that uses an authenticated web filter. I have configured eclipse/svn etc to use the http proxy when i work in this environment. The jira/bugzilla mylyn connectors, eclipse update, svn etc continue to work because of those settings.

Unfortunately the unfuddle mylyn connector does not appear to use those settings.

I used wireshark to track network activity when the unfuddle connector validated my info. Wireshark reported a ton of attempts to directly connect to 174.129.246.232:80. 174.129.246.232 resolves to ec2-174-129-246-232.compute-1.amazonaws.com and unfuddle.com. I can only assume that this is the unfuddle connector.

I confirm this bug, we have the same problem here, it assumes a direct connection but does not work if we are behind a proxy.

Is there a workaround for this problem?