Re: managing proxy settings under OS X

Subject: Re: managing proxy settings under OS X
From: Quinn <email@hidden>
Date: Thu, 22 Mar 2001 11:36:56 -0800

At 8:48 -0600 20/3/01, Joey Gray wrote:

with all of the appropriate error checking not shown here. under Mac OS 9,
it works great; but under OS X i get a -667 error from the ICSetPref() call.

This is a known limitation of the IC API on Mac OS X. I talked with the guy working on this and here's his response.

At 10:56 -0800 22/3/01, Curt wrote:

Yes, we have to go through another framework to get to and set the proxy settings. On OS X there is the concept of interfaces, you can see this by going into the Network Preference pane of SystemPreferences.app. Typically there are interfaces such as 'Built in Ethernet', 'Airport' and 'Modem'. Furthermore, to set these system-wide preferences, one must authenticate themselves as the root user.

Since we don't have UI to do this in InternetConfig on X (for example, which interface do you want the proxy settings to be applied to, and are you really the root user?) -- and this hit us pretty close to GM -- we decided the best solution would be to tell users to set the proxy information themselves in SystemPreferences. The alternative was that IC would allow you to set these, but it wouldn't sync with the rest of the system (i.e. not everything would get these settings).

Getting these preferences with ICGetPref will work, it is just setting them that is prohibited.

The keys that are affected by this in GM are:
kICFTPProxyHost
kICGopherProxy
kICHTTPProxyHost
kICUseFTPProxy
kICUseGopherProxy
kICUseHTTPProxy
kICUseSocks

Furthermore, in the release after GM, these keys will also go through SystemPreferences and subject to the same limitation:

kRTSPProxyHost
kSocksHost
kNoProxyDomains
kUsePassiveFTP
kUseRTSPProxy

I apologize for the lack of documentation on this, we'll try to get stuff up. We're also looking at better ways to do this.

Setting these preferences on Mac OS X requires you to work with the SystemConfiguration framework, which is a private framework that is not supported for external developers in Mac OS X 10.0. You're probably familiar with the issues related to the use of SystemConfiguration framework already. If not, write back to the list and I'll describe in in gory detail.

S+E
--
Quinn "The Eskimo!" <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware

Follow-Ups:
- Re: managing proxy settings under OS X
  - From: Joey Gray <email@hidden>

References:
	>managing proxy settings under OS X (From: Joey Gray <email@hidden>)

Prev by Date: Asynchronous OTRcv & OTTimerTasks
Next by Date: Re: IPv6 and MacOS X
Previous by thread: managing proxy settings under OS X
Next by thread: Re: managing proxy settings under OS X
Index(es):
- Date
- Thread

Home