Simon Heywood wrote:
Sorry for the delay in replying back, been busy developing with Shoes.
Responses below
On Wed, Dec 10, 2008 at 11:14 PM, _why <[email protected]
<mailto:[email protected]>> wrote:
Would it help if I borrowed IE's proxy settings if HTTP_PROXY isn't
defined? You see, I already had it in mind to do that. Or would I
need to parse the PAC myself?
In this instance, yes it would certainly help me, but I might just be an
oddball case, so if the consensus was use the HTTP_PROXY environment
variable then so be it.
I would say that in no way are you an oddball case. The HTTP_PROXY
environment variable is not usually set in a windows environment. Most
users will just set the system (IE) proxy settings, and pretty much
everything gets its proxy configuration from that.
I think it would be beyond awesome if on all platforms, Shoes would grab
the system proxy settings if HTTP_PROXY isn't set (but you'd probably
need a way to override that behavior for testing), since if one is
distributing an application, that's what the user will expect. (Most
users will be like what's this environment variable stuff? If you tell
them that's why the app isn't working)
As to whether you'd have to parse the PAC file yourself, I'm afraid I'm
too ignorant to help you there. I would hazard a guess as to 'yes', in
which case this is seeming like a lot of work just to solve my problem.
I know that on Mac OS X (it's been awhile, tho, so this may have
changed), you do have to parse the PAC file yourself. However, if the
system is setup for a manual proxy configuration, then you can just grab
the proxy host and port. I believe that parsing the PAC file is a
non-trivial operation, since it is pretty much just an arbitrary
JavaScript file.
--
Bem Jones-Bey ([email protected])
