Quote:
Originally Posted by waces
corrects me if i'm wrong (frankly not dig myself deep into the metadata query, so feel free to correct me) but the data query is a simply http get via port 80 so see no reason why it cannot work. Pac file only route the traffic to a proxy (if available) or use "direct" connection (with no proxy) if the proxy server not available. So, in this case as the client not able to connect to the proxy server on off-corporate network the traffic will simply bypass the pac file settings. As of it I see no reason to fail. But, as I mentioned, I more than happy if someone directs me to the right direction and probably make me able to find a quick fix for the issue
|
Are you sure about that for the PAC file usage? I would have expected that if the PAC file was not available, or the proxy it specified was not available, you wouldn't be able to access the URL using the client. If you were able to, it could be considered a security issue in a lot of corporate environments. I'm not sure on this as I've never set one up.
To use a PAC file, the client must:
- Have a way to configure the URL to retrieve the PAC file.
- Retrieve the PAC file.
- Each time the client wants to access a URL, it has to call the Javascript function in PAC file passing the URL and host name.
- Then interpret the results of the call to decide whether to access the URL directly or via the returned proxy.
- Handle when the proxy server is not available.
None of that is hard, but it takes time develop, test and maintain. And the client has to be able to execute Javascript. The latter makes PAC file support for most clients undesirable for most projects. With that, I can understand why Kovid doesn't want to support them.