curl-users
a problem
Date: Fri, 12 Jul 2002 11:06:32 -0400
Hi all,
I am new to curl and having a really hard time doing something that
appears to be simple:
I am attempting to get a file off of a secure web site....
I have the latest version of curl:
curl -V
curl 7.9.8 (i586-pc-linux-gnu) libcurl 7.9.8 (OpenSSL 0.9.6b)
I am running red hat 7.3
here is my curl command:
curl -A "Mozilla/4.0" -L -i -v -get -d testdoc.out -u
<username>:<passwd> https://xx.xxx.xxx.xxx/testdoc.out
below is the output :
HTTP/1.1 302 Found
Date: Fri, 12 Jul 2002 14:59:03 GMT
Server: Apache/1.3.12 (Win32) mod_ssl/2.6.4 OpenSSL/0.9.6
SecureTransportWWW/3.0.3
Set-Cookie: FDX=PS7ut8CoPQcAAAjUPS4; path=/
Location:
https://xx.xxx.xxx.xxx:443/testdoc.out?&STCO=1PS7ut8CoPQcAAAjUPS4&STCOEND^M
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
HTTP/1.1 302 Found
Date: Fri, 12 Jul 2002 14:59:05 GMT
Server: Apache/1.3.12 (Win32) mod_ssl/2.6.4 OpenSSL/0.9.6
SecureTransportWWW/3.0.3^M
Set-Cookie: FDX=PS7ut8CoPQcAAAjUPS4; path=/
Location:
https://xx.xxx.xxx.xxx/testdoc.out?&STCO=2PS7ut8CoPQcAAAjUPS4&STCOEND^M
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
HTTP/1.1 302 Found
Date: Fri, 12 Jul 2002 14:59:07 GMT
Server: Apache/1.3.12 (Win32) mod_ssl/2.6.4 OpenSSL/0.9.6
SecureTransportWWW/3.0.3^M
Set-Cookie: FDX=PS7ut8CoPQcAAAjUPS4; path=/
Location: https://xx.xxx.xxx.xxx/testdoc.out
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
HTTP/1.1 401 Authorization Required
Date: Fri, 12 Jul 2002 14:59:10 GMT
Server: Apache/1.3.12 (Win32) mod_ssl/2.6.4 OpenSSL/0.9.6
SecureTransportWWW/3.0.3
WWW-Authenticate: Basic realm="FileDriveWWW"
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>401 Authorization Required</TITLE>
</HEAD><BODY>
<H1>Authorization Required</H1>
This server could not verify that you
are authorized to access the document
requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.<P>
I am leaning towards a cookie problem but I am not sure...... if anyone
has any suggestions, ideas or things to do/try please let me know!
thanks a lot!
dougc
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Gadgets, caffeine, t-shirts, fun stuff.
http://thinkgeek.com/sf
Received on 2002-07-12