Dan,

Any proxy servers set up? Check the man page for curl under the ENVIRONMENT section, maybe it is wrongly picking up a proxy server there that's not working...? (I'm kinda stabbing in the dark here to find an answer...)

No, on second thought, that wouldn't be it because curl would exit with (5): Couldn't resolve proxy...

Is wget configured to use a proxy? Anything interesting in /usr/local/etc/wgetrc, /etc/wgetrc, or ~/.wgetrc?

-Josh

-----------
Due to the recent increase in spam and falsely sent email, I now PGP Sign all of my outgoing mail to prove my identity. This means that you will see an attachment called "PGP.sig" with this message. This attachment can be used to prove that I am who I say I am. If you are not familiar with PGP, you can safely ignore it. For more information, please visit http://www.pgp.com/ or http://www.gnupg.org/




On Mar 4, 2005, at 9:02 AM, Dan Monjar wrote:

William Sutton wrote:
port blocking at $WORK? I know we have a corporate filter which requires signing on to open the ports. Kinda sucks when one wants to add Perl modules to ActiveState and has to go to the ActiveState web site so that the coporate filter allows the non-browser network traffic.
William

more than likely... but I run the $WORK firewall so if I could figure out what to open I would. What puzzles me is why wget works but curl doesn't.

--
Dan Monjar
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc

Attachment: PGP.sig
Description: This is a digitally signed message part

-- 
TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ  : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc

Reply via email to