Bug 158600

Summary:	https_proxy is not imported by gconf
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Wolfgang Rosenauer <wolfgang.rosenauer>
Component:	GNOME	Assignee:	Federico Mena Quintero <federico>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	Beta 8
Target Milestone:	RC 1
Hardware:	Other
OS:	SuSE Linux 10.1
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Wolfgang Rosenauer 2006-03-16 11:45:29 UTC

The "secure_host" setting is empty but https_proxy is set
correctly in the environment.

Comment 1 Wolfgang Rosenauer 2006-03-16 12:06:29 UTC

control-center2-system-proxy-configuration.diff is from Federico.
The key is defined in the patch:
+#define KEY_SECURE_HOST                                "/system/proxy/secure_host"                     /* string */
+#define KEY_SECURE_PORT                                "/system/proxy/secure_port"                     /* int */

but the settings are never read or written :-(

Comment 2 Federico Mena Quintero 2006-03-21 01:59:11 UTC

Is HTTPS_PROXY relatively new in Yast?  I'll add support for this to our patch.

Comment 3 Wolfgang Rosenauer 2006-03-21 05:56:30 UTC

I *guess* it wasn't there in NLD9 or 9.3. It was added later especially since YOU need it for accessing you.novell.com to get updates for business products. Anyway, thanks for fixing it.

Comment 4 Federico Mena Quintero 2006-03-23 01:45:51 UTC

Fixed on the latest version.

* Wed Mar 22 2006 - federico@novell.com
- Updated control-center2-system-proxy-configuration.diff to fix bug
  #158600.  Gnome-settings-daemon will now read the HTTPS_PROXY value
  from /etc/sysconfi/proxy and set it in the appropriate GConf keys.