Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 351397 - [Net] Proxy settings are not used in manual mode
Summary: [Net] Proxy settings are not used in manual mode
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-07 04:23 EDT by BlackBishop64 CLA
Modified: 2019-11-14 03:08 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description BlackBishop64 CLA 2011-07-07 04:23:50 EDT 
Build Identifier: I20110613-1736

Proxy settings are not used in manual mode, org.eclipse.core.net.prefs file have to be edited manually in order to change the property systemProxiesEnabled to true, only in that case eclipse recognize proxy settings.

Otherwise a lot of error messages "!MESSAGE System property https.proxyHost is not set but should be XXXXXX" appear when trying to update or install new software

Reproducible: Always

Steps to Reproduce:
0. Install eclipse from scratch
1. Set connections settings to manual
2. Configure proxy settings with authentication
3. Try to update or install new software
Comment 1 Lars Vogel CLA 2019-11-14 03:08:05 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.