Bug 549143 - Improve HTTP Proxy handling for "manual" proxy settings and "native" at all
Summary: Improve HTTP Proxy handling for "manual" proxy settings and "native" at all
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.12   Edit
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-10 10:25 EDT by Albert Tregnaghi CLA
Modified: 2023-07-07 15:20 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Albert Tregnaghi CLA 2019-07-10 10:25:57 EDT
Situation:
 - being inside a company, having internet access only by HTTP proxy (no SOCKS)
 - Network is not slow (min 16 MBit/s up to 300Mbit/s)

Problem:
 - Even when using CNTLM (means no password or username for localhost
   intermediate proxy) and configured "manual" proxy settings in network 
   preferences I often have still network/proxy issues. Any other application
   than eclipse works well with my CNTLM.

Examples:
 - Tip of the day: Slow but working but the Twitter parts do often either not
   or show up very slow
   (unfortunately twitter parts are the first ones...)
 - Welcome page: Ultra slow (I think this could be a proxy issue as well)
   in combination with https://bugs.eclipse.org/bugs/show_bug.cgi?id=549136
   this is was very unconvenient
 - Switching to "manual" I also got always the information in error log
   "System property https.proxyPort is not set but should be <portNr>."
   but I configured https correctly and it is working (at least marketplace)
   so ... no idea why the log enry comes up
 - I work on Linux (Ubuntu based) and on Windows machines with Eclipse. 
   In conjuction with a HTTP company network proxy, I have never had the 
   situation that "native" proxy setting has worked. So I am not sure 
   how this is supported at all
 - Overriding the eclipse.ini with -Dhttp.... setup did also not work at all
 - Even when marketplace is working other parts are still having problem
   e.g. Tip of the day (Twitter part) Internal Browser view -> 
   seems not to use the setup in preferences,
 - The eclipse installer did not work for me behind the company HTTP proxy as
   well, no matter what I was setting up in proxy settings: I did not work
   (... well this was 2 years ago... so...)

The proxy handling done in IntelliJ seems to be much more smarter. Many of my colleagues became frustrated with eclipse (proxy) problems and switched to IDEA.

I think this is something very important and should be improved.
As a user an IDE shall be a "runs out-of-the-box" experience .

Possible solution:
 - Eclipse comes always up with native components (e.g. SWT). So why is there
   no native fetch (at launcher time?)for existing https_proxy settings from
   running OS or getting information about system settings ( at least at linux
   this should work well)?
 - Having SWT access, we have access to System Browser. Is there no way to
   use in "native" mode the setup of the system browser? 
 - ...
Comment 1 Eclipse Genie CLA 2021-07-16 06:06:59 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2023-07-07 15:20:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.