Hi!
I'm behind a proxy here, and I'd like to use the blogging bundle. Unfortunately, there's not much of information on this in the internet, so could someone here help me out?
My favourised solution would be that TM takes over the system proxy out of OS X's "Location"s. But a hint on how to set the proxy via env would help, too :-)
TIA
André
* Bonhôte André andre@bonhote.org [2007-03-30 06:48]:
I'm behind a proxy here, and I'd like to use the blogging bundle. Unfortunately, there's not much of information on this in the internet, so could someone here help me out?
Set TM_HTTP_PROXY to host:port. Other environment variables that affect the bundle are in the help file. Run the Help command in the Blogging bundle.
My favourised solution would be that TM takes over the system proxy out of OS X's "Location"s.
The proxy information is in /Library/Preferences/SystemConfiguration/preferences.plist, but it lists all the network interfaces and I'm not sure how to tell which one will be used.
On 30. Mar 2007, at 17:07, Grant Hollingworth wrote:
My favourised solution would be that TM takes over the system proxy out of OS X's "Location"s.
The proxy information is in /Library/Preferences/ SystemConfiguration/preferences.plist, but it lists all the network interfaces and I'm not sure how to tell which one will be used.
There is a Support/bin/proxy_config command which I made to dump the proxy settings, and it was my intent to make the various bundle commands use this (preferably through some wrapper -- I wonder why curl and friends are not modified on OS X to use the system wide proxy settings?).
Unfortunately this user/pass/port is not enough for some proxies (where you login or have auto config/discovery or something like that). I don’t have a proxy myself, and I have no experience with them, so this project to update the bundles to support proxies, quickly stranded.
On 30.03.2007, at 17:07, Grant Hollingworth wrote:
- Bonhôte André andre@bonhote.org [2007-03-30 06:48]:
I'm behind a proxy here, and I'd like to use the blogging bundle. Unfortunately, there's not much of information on this in the internet, so could someone here help me out?
Set TM_HTTP_PROXY to host:port. Other environment variables that affect the bundle are in the help file. Run the Help command in the Blogging bundle.
Shift, a real RTFM issue :) Sorry, didn't consult that one.
My favourised solution would be that TM takes over the system proxy out of OS X's "Location"s.
The proxy information is in /Library/Preferences/ SystemConfiguration/preferences.plist, but it lists all the network interfaces and I'm not sure how to tell which one will be used.
It's not only a TM issue. IMHO, Firefox, Terminal.app and all the others should be able to take over the system's settings. Maybe we should wait for Leopard ...
Thanks
André
On 31.03.2007, at 16:55, Allan Odgaard wrote:
On 30. Mar 2007, at 17:07, Grant Hollingworth wrote:
My favourised solution would be that TM takes over the system proxy out of OS X's "Location"s.
The proxy information is in /Library/Preferences/ SystemConfiguration/preferences.plist, but it lists all the network interfaces and I'm not sure how to tell which one will be used.
There is a Support/bin/proxy_config command which I made to dump the proxy settings, and it was my intent to make the various bundle commands use this (preferably through some wrapper -- I wonder why curl and friends are not modified on OS X to use the system wide proxy settings?).
Yup, sucks definitely.
Unfortunately this user/pass/port is not enough for some proxies (where you login or have auto config/discovery or something like that). I don’t have a proxy myself, and I have no experience with them, so this project to update the bundles to support proxies, quickly stranded.
I have been working with different proxies (squid, cacheflow, ms proxy) for quite a while, and I always only needed hostname:port to connect to them. I guess having user:pass@host:port in the bundles solves the proxy madness in around 80% of the cases - might be worth continuing on this track.
Cheers
André
On 2. Apr 2007, at 08:13, Bonhôte André wrote:
[...]
Unfortunately this user/pass/port is not enough for some proxies (where you login or have auto config/discovery or something like that). I don’t have a proxy myself, and I have no experience with them, so this project to update the bundles to support proxies, quickly stranded.
I have been working with different proxies (squid, cacheflow, ms proxy) for quite a while, and I always only needed hostname:port to connect to them. I guess having user:pass@host:port in the bundles solves the proxy madness in around 80% of the cases - might be worth continuing on this track.
I added the following page to the wiki: http://macromates.com/wiki/ ToDo/Proxy
It seems that curl (and presumably other shell commands) understand the http_proxy environment variable (found out from here [1]).
I have made room for a list of commands that does not work with proxies (when this variable is set). So proxy users, please add to the list if there are commands you find not working.
[1]: http://www.macosxhints.com/article.php?story=20070424075935936
-
Allan Odgaard -
Bonhôte André -
Grant Hollingworth