On Mon, 20 May 2002 esp5_at_rama.comp.pge.com wrote:

> > In your corporate environment can you really not simply hard code a proxy
> > server (or two)?
>
> No... that doesn't work. (tried it already). You need to go through the
> automatic server - at least the way they've set it up here, the end-proxies
> only accept connects from the central proxy, and the end proxies send back
> a direct connection to your local workstation.

Hm, the pac config is used by the browser to get a host name or IP for the
proxy to use (or "DIRECT" if no proxy is to be used).

Most pac javascript programs are very simple and fairly easy to read and
understand by human eyes.

Extracting the proxy from there and using in a curl command line should be
perfectly possible, and the proxy can't know if we used the PAC file or not.
I don't understand how this can't work. I'd rather guess that something else
is failing in that case.

> Trying to bypass any of this is prohibited, because for one, they don't
> want you to work around their 'protections' against people 'accessing
> inappropriate sites'. And since websense is pretty common, (and will get
> more common as networks do filtering) this results in a *huge* usability
> hole for curl.

While you might look at it that way, I tend to look at it from the other
direction. The "usability hole" is created by the admins that force you to
live inside such fences.

And as was already pointed out: we certainly don't mind if anyone would fix
this "hole" and provide this functionality in (lib)curl. It is not just a
quick patch though. This needs some careful thinkning and some pretty large
chunk of code.

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm