Community
Participate
Working Groups
Created attachment 132729 [details] 3.4.2 Proxy configuration I have a 3.4.2 installation and a 3.5M6 installation. With 3.4.2 I am correctly accessing cvs :extssh:kmitov@proxy.eclipse.org:443/cvsroot/webtools with the following proxy configuration (first screen shot attached) With 3.5M6 I can not access the same cvs :extssh:kmitov@proxy.eclipse.org:443/cvsroot/webtools with the following proxy configuration (second screen shot attached) I suppose (haven`t debug) the problem is in the UI of the Network Connections preference page and that is way I am opening the bug here. The 3.5 preference page is missing SSL proxy field (or I could not find it) which I think is needed for extssh connection. Best Regards, Kiril
(In reply to comment #0) > with the following proxy configuration (second screen shot attached) Where is it? :)
Created attachment 132755 [details] Second proxy configuration Here it is :). I had a "network" problem
Kiril, please launch Eclipse with "-console" switch which gives an access to the OSGi console. Then collect all of the properties (command "props") that contain "proxy" in its key and attach then to the bug.
http.nonProxyHost = localhost|127.0.0.1 http.proxyHost = proxy http.proxyPort = 8080 http.proxySet = true https.nonProxyHost = localhost|127.0.0.1 https.proxyHost = proxy https.proxyPort = 8080 https.proxySet = true socksProxyHost = proxy socksProxyPort = 8080
Created attachment 132759 [details] The Error I have not attached the actual error. Here it is
Thanks for the information. Does anything appear in the error log view?
(In reply to comment #6) > Thanks for the information. Does anything appear in the error log view? > No. The error log is empty.
Kiril, what about accessing other resources through the proxy? Are you able to perform an update via p2?
(In reply to comment #8) > Kiril, what about accessing other resources through the proxy? Are you able to > perform an update via p2? > I have just installed an execution environment description from http://www.eclipse.org/pde/pde-api-tools/updates/. The installation was successful except for one exception: But I suppose this is not related to this bug. org.eclipse.equinox.internal.provisional.p2.core.ProvisionException: Unable to read repository at file:/D:/tmp/31/eclipse/p2/org.eclipse.equinox.p2.metadata.repository/cache/content1048691197.jar. at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryIO.read(MetadataRepositoryIO.java:73) at org.eclipse.equinox.internal.provisional.spi.p2.metadata.repository.SimpleMetadataRepositoryFactory.validateAndLoad(SimpleMetadataRepositoryFactory.java:119) at org.eclipse.equinox.internal.provisional.spi.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:88) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:54) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:659) at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:607) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:88) at org.eclipse.equinox.internal.provisional.p2.ui.QueryableMetadataRepositoryManager.doLoadRepository(QueryableMetadataRepositoryManager.java:57) at org.eclipse.equinox.internal.provisional.p2.ui.QueryableRepositoryManager.loadRepository(QueryableRepositoryManager.java:191) at org.eclipse.equinox.internal.provisional.p2.ui.QueryableRepositoryManager.loadAll(QueryableRepositoryManager.java:108) at org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$2.run(PreloadingRepositoryHandler.java:69) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.io.IOException: Premature end of file. at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryIO$Parser.parse(MetadataRepositoryIO.java:206) at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryIO.read(MetadataRepositoryIO.java:55) ... 12 more
(In reply to comment #9) > But I suppose this is not related to this bug. It's not. Seems like the problem exists only when accessing the proxy server via CVS client. Adding Atsuhiko to the CC list to comment.
(In reply to comment #5) > Created an attachment (id=132759) [details] > The Error > > I have not attached the actual error. > > Here it is It seems that Socks proxy has been choosed. How about unchecking Socks on "Second proxy configuration"?
(In reply to comment #11) > It seems that Socks proxy has been choosed. > How about unchecking Socks on "Second proxy configuration"? > I can not uncheck SOCKS. I am clicking on the check box, but it does not "react".
(In reply to comment #12) > I can not uncheck SOCKS. I am clicking on the check box, but it does not > "react". You can clear the SOCKS entry, it's enough. Checkboxes only map the active provider with entries in the table.
(In reply to comment #13) > You can clear the SOCKS entry, it's enough. Checkboxes only map the active > provider with entries in the table. > It works. If I clear the SOCKS entry I am able to connect to cvs.
Kiril, Atsuhiko, any comments or suggestions what to do with the bug? Could we take any action to prevent this from happening in the future?
(In reply to comment #15) > Kiril, Atsuhiko, any comments or suggestions what to do with the bug? Could we > take any action to prevent this from happening in the future? > I would suggest to: 1. Make the checkboxes that can not be checked/unchecked disabled. This would mean "They are check but you can not change this". 2. When the user click Edit a dialog is open. A short description of what SOCKS means could be added in this dialog and how changing this value would affect the end user. The rest of making it work depends on the user and his knowledge (in this case my lack of knowledge:) ).
Created attachment 133565 [details] Screen_01 I tried to grey out the checkboxes but the result looks odd, see the attachment. Probably better way to do it would be changing the checkboxes to icons.
(In reply to comment #17) > I tried to grey out the checkboxes but the result looks odd, see the > attachment. Probably better way to do it would be changing the checkboxes to > icons. > The look depends on the graphical environment and the operating system. In this case the odd look really means that they are disabled. Another point. Do we really need the checkboxes? They can not be checked/unchecked. Probably the whole column could be removed and set an appropriate color or the rolls.
(In reply to comment #18) > Another point. Do we really need the checkboxes? They can not be > checked/unchecked. Probably the whole column could be removed and set an > appropriate color or the rolls. At this point we should not touch this UI. We can continue improving the proxy area in 3.6.
(In reply to comment #16) > 2. When the user click Edit a dialog is open. A short description of what SOCKS > means could be added in this dialog and how changing this value would affect > the end user. I disagree. We assume that an user that sets this field is aware of the changes he's doing. Moreover this is not an Eclipse concept. If we did provide a message in such cases then whole UI would be cluttered with them.
(In reply to comment #16) > 1. Make the checkboxes that can not be checked/unchecked disabled. This would > mean "They are check but you can not change this". This will be included along with the fix for other bug. See bug 257443, comment 21 for details.
As reported this bug is INVALID, marking it appropriately.
*** Bug 272813 has been marked as a duplicate of this bug. ***
