cURL / Mailing Lists / curl-users / Single Mail

curl-users

strange proxy related curl error on mac os x

From: Henning Grote <henning.grote_at_gmail.com>
Date: Wed, 24 Oct 2007 21:56:17 +0200

whlie trying to use MoodBlast <http://tinyurl.com/2aj34w> I stumbled
upon a curl error, which I was unable to resolve myself.

(I am not a *nix geek and this is my first post to curl-users, please
be patient)

Setup:
PowerBook G4, 1GB, 1,5Ghz, 80Gig HD
Mac OS 10.4.10
curl 7.13.1 (powerpc-apple-darwin8.0) libcurl/7.13.1 OpenSSL/0.9.7l
zlib/1.2.3
Protocols: ftp gopher telnet dict ldap http file https ftps
Features: IPv6 Largefile NTLM SSL libz

The MoodBlast developer has tried to debug it with the following
applescript:

global twitter_login

set twitter_login to "twitter_username:passwort" -- replace with your
info
my set_twitter("testing%20from%20Applescript") -- you can edit the
quoted paramater, just url escape it

on set_twitter(status)
        set the_status to quoted form of ("status=" & status)
        try
                global twitter_login
                set twitter_results to do shell script "curl --user " &
twitter_login & " --data-binary " & the_status & " http://twitter.com/
statuses/update.xml"
                try
                        tell application "System Events"
                                set xmlDocument to make new XML data with data twitter_results
                                set successTwitter to value of XML element 3 of XML element 1 of
xmlDocument
                        end tell
                        return {true, successTwitter}
                on error msg
                        return {false, "XML Error: " & twitter_results}
                end try
        on error msg
                return {false, "Retrieve error:" & msg}
        end try
end set_twitter

The Script outputs the following error message:

{false, "Retrieve error:
curl: (5) Couldn't resolve proxy 'www-proxy.hamburg.xxx.de'"}

The same script reports success, when run under the Admin account.

The funny thing is: I have a blank .curlrc in my home directory, (not
the admin account). The proxy mentioned in the error message is one
from a long deleted network location. Neither in my current network
location nor in any other network location is a proxy defined
(checked that more than once)

 From which locations does curl get informations about which proxies
to use - other than .curlrc? There must be some other config-files in
my home directory where curl gets the outdated information about the
proxy.

And, regarding the blank .curlrc, what would be the correct syntax in
the .curlrc to force curl to use no proxy?

I tried NO_PROXY=*, NO_PROXY="*" but got error messages both times
(told you, I am not a geek ;-)

I would appreciate any helpful answers.

Henning Grote
Received on 2007-10-24