Aperture does not seem to use the proxy settings
Behind a firewall, the authentication works (the current list of tags in flickr is correctly imported), but it seems that when trying to export the proxy settings set in the macos preferences do not work (while it does with safari and other internet related softwares) as I get a lot of messages in console.app that say basically that the proxy is not set (this is the default HTML page one gets when the proxies are not correctly set).
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has a solution in progress.
-
Inappropriate?If your proxy requires authentication, FlickrExport doesn't support that. Otherwise it should use the same proxy settings as the OS.
Can you paste an error message from Console into this thread? -
Inappropriate?Basically, it is an HTML page containing
[...]
<h1>Your Browser is Misconfigured</h1>
<h2>Please follow these instructions</h2>
How To Configure Your Browser
[...]
which is a link to how to set the proxy (automatic configuration with a PAC file). Note that the proxy does not require authentication. -
Inappropriate?Hmm. FlickrExport uses the SystemConfiguration framework to retrieve the proxy settings, so it's using whatever the OS says - unless perhaps PAC-based setups don't get passed on in the same way.
If you enter the proxy information manually to System Preferences, does it work?
1 person says
this solves the problem
-
Inappropriate?I tried, and yes it does work. Great!
Do you want me to send you the proxy PAC file?
Just in case, I also tried to modify it so the PAC file returns all the time the same proxy server, but this did not work...
-
Inappropriate?12/12/2008 11:13:35 Aperture[484] HTTP Error: sendSynchronousRequest returned nil.
12/12/2008 11:13:36 Aperture[484] HTTP Error: sendSynchronousRequest returned nil.
-
Inappropriate?If you could mail me your PAC files (if you have access to them) that might help.
I suspect the issue is out of my hands in that FlickrExport queries the SystemConfiguration framework for the active proxies, and there might be a bug in the OS not sending on that info when a PAC is in use.
Also, sorry for the hideously tardy reply.
I’m sorry to have let this one slip.
-
Inappropriate?This is the pac file
function FindProxyForURL(url,host)
{
// Hostname without domainname or host within our own domain?
// Try them directly:
var lchost=host.toLowerCase();
if ( isPlainHostName(host)||
dnsDomainIs( host,".gla.ac.uk")||
localHostOrDomainIs(lchost,"127.0.0.1") ||
shExpMatch(url, "connect:*:563") ||
shExpMatch(url, "connect:*:443") ||
shExpMatch(url, "connect:*:444") ||
shExpMatch(url, "https:*:*")
)
return "DIRECT";
// First try proxy1 then proxy2.
// If one of 'm is down the client will try the other server.
else
return "PROXY wwwcache.dcs.gla.ac.uk:8080; PROXY wwwcache.gla.ac.uk:8080";
} -
Inappropriate?Hehe. I used to work and study at Glasgow Uni. It does not surprise me that wwwcache.gla.ac.uk is problematic....
Will look into it.
I’m amused
-
Inappropriate?I too have found the problem to occur with PAC files (still — not sure if you/Apple have done anything to resolve this since the bug was reported?)
If I set the proxy manually, it works fine (which I was very pleased to discover) but I still feel the PAC file should be workable...
My pac file can be found at http://www.usyd.edu.au/proxy.pac (I'm fairly sure it's publicly accessible)
I’m thankful it works with manual settings at least...
-
Inappropriate?Andrew,
As far as I know, the problem is still outstanding. Mac OS X doesn't pass through the PAC-set proxy settings when FlickrExport queries the system for proxy information.
Sorry. -
Inappropriate?Fraser,
I'm not personally a Mac OS X developer (at least, not outside the C++ std lib) so I may well be missing the point / making some invalid assumptions... so if I'm telling you something totally irrelevant or something you already know all about please don't take offence (:
Having looked into other applications that don't support PAC files but do support a manually set proxy, I came across some documentation that suggested to me that the method of getting the proxy from a PAC file was quite different to when it was manually set in the network preferences. Because a PAC file is just a script that lets you set a proxy based on the URL being accessed (i.e. depending on both your own and the destination host/port) there's no sensible response for a "GetProxy()" type function (without supplying a URL). Instead, the URL needs to be passed through the PAC script to determine the proxy settings.
Anyway, you may have already looked into this and I might be totally off the mark (i.e. I have no idea which API(s) you have access to for plug-ins!), but on the off-chance that the problem is a complex or non-intuitive API, I thought I'd mention this...
These links/examples might be helpful (or at the very least a better explanation than I've managed):
- http://developer.apple.com/mac/librar...
- http://developer.apple.com/mac/librar... -
Inappropriate?Andrew,
That's really very useful. Thank you. It seems that the APIs in question appeared in 10.5 (and some in 10.6). At the moment, FlickrExport 3 has to support 10.4 systems but, according to the road map that I published recently, 10.4 support will be going away in FlickrExport 3.5.
Hopefully in that time frame I can look at using these APIs for PAC support.
Best,
Fraser
I’m happy
Loading Profile...



EMPLOYEE
