• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WPAC configuration in Tiger (and beyond)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WPAC configuration in Tiger (and beyond)


  • Subject: Re: WPAC configuration in Tiger (and beyond)
  • From: Jeremy Wyld <email@hidden>
  • Date: Fri, 5 Aug 2005 08:48:35 -0700

The proxy dictionary does nothing more than hold the settings as produced by the user and saved by the Network Preferences pane. After verifying that the checkbox for PAC is turned on, you should see a couple entries in the dictionary, "ProxyAutoConfigEnable" and "ProxyAutoConfigURLString." "ProxyAutoConfigEnable" should have a value of 1. This will indicate that the PAC should be used. It's up to you to determine how all these should be used. Now if these settings are not being flushed out to SystemConfiguration, make sure you file a bug.

Now, if you use CFNetwork for performing a HTTP or FTP request, it will interpret the dictionary and will make automatic use of the settings. To see how and in what order it chooses to interpret that dictionary, I suggest reading the code directly at http:// darwinsource.opendarwin.org/10.4.2/CFNetwork-128.2/Proxies/ ProxySupport.c and you can see how everything comes into play.

If you are not using CFNetwork or are below HTTP/FTP, you'll need to do the work yourself. I would then suggest filing an enhancement to have CFNetwork export a function which does the heavy lifting. I don't see any particular reason why such a function or such support couldn't be exported.

jeremy


On Aug 5, 2005, at 8:26 AM, Nathan Herring wrote:

[Originally sent to CarbonIT before I realized this list existed.]

Our IT department has a PAC file for use with our Windows browsers.
However, if in 10.4.2, I try and set my proxies "Using a PAC file",
nothing works outside of the firewall.

The CFDictionary information we use to connect shows a bunch of the
proxy server information correctly set in, but the XXXXEnable setting is
false, and we use that to determine whether or not to use that proxy
server.


Q: Is it a known issue that the proxy settings don't quite configure
correctly?

Q: How do you differentiate between internal servers (i.e. proxy
exceptions) and others?

AFAICT, unless you meta-interpret the Java script to extract the known
proxy exceptions, there's no good way to build the list -- you just have
to ask the script how to connect to server X for each server X.


What is the future direction of development here? Should we (as network
applications writers) be expected to use PAC files? Or will Apple
provide a functional intermediate layer above the PAC file? Or will the
proxy settings dictionary eventually "just work"?


TIA,
nh

----
Nathan Herring
MacBU SDE/Development


<bowlderized_wpad.dat>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: WPAC configuration in Tiger (and beyond)
      • From: Nathan Herring <email@hidden>
    • Re: WPAC configuration in Tiger (and beyond)
      • From: David Young <email@hidden>
References: 
 >WPAC configuration in Tiger (and beyond) (From: Nathan Herring <email@hidden>)

  • Prev by Date: WPAC configuration in Tiger (and beyond)
  • Next by Date: Re: WPAC configuration in Tiger (and beyond)
  • Previous by thread: WPAC configuration in Tiger (and beyond)
  • Next by thread: Re: WPAC configuration in Tiger (and beyond)
  • Index(es):
    • Date
    • Thread