216638 – Change request for "Network Connections" preference page

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 216638 - Change request for "Network Connections" preference page

Summary: Change request for "Network Connections" preference page

Status:	RESOLVED DUPLICATE of bug 204563

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	Team (show other bugs)
Version:	3.4
Hardware:	All All

Importance:	P3 major (vote)
Target Milestone:	---
Assignee:	Platform Team Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2008-01-25 15:51 EST by Cathy Kegley
Modified:	2008-01-29 09:06 EST (History)
CC List:	3 users (show)

See Also:

Attachments
UI update for network connection pref page (34.62 KB, image/jpeg) 2008-01-25 15:53 EST, Cathy Kegley	no flags	Details
View All 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 Cathy Kegley

2008-01-25 15:51:39 EST

The "Network Connections" preference page and underlying infrastructure should provide the capability for a user to configure automatic proxy.  This would mimic the proxy functionality in a browser.  The additions to the UI would include a radio button for that option as well as a text field for the address of the proxy configuration file.  See attached screen shot for example.

Comment 1 Cathy Kegley

2008-01-25 15:53:16 EST

Created attachment 87912 [details]
UI update for network connection pref page

Comment 2 Raji Akella

2008-01-25 16:25:14 EST

What are the chances of getting this in 3.4?

Comment 3 Benjamin Pasero

2008-01-26 12:53:48 EST

I would love to see this in 3.4. There should also be a way of chosing to using the system defined proxy settings (e.g. on Windows they are stored in the registry).

Comment 4 Szymon Brandys

2008-01-29 09:06:46 EST

This bug is actually a duplicate of bug 204563 and bug 180921. I'm marking it as a duplicate of bug 204563 cause the initial comment was related to it.

There is no plan to address 204563. This is a helpwanted issue and any contribution are welcome. I've been considering to address 180921 though during 3.4.

*** This bug has been marked as a duplicate of bug 204563 ***