curl-and-python

Re: Help Converting curl.exe command to pycurl

From: Peter Schott <pschott_at_drivefinancial.com>
Date: Wed, 25 May 2005 16:48:11 -0500

I'm using the certificate given. Got a bunch of debug data (kudos to
whoever did this in their code first. From what I can see, it connects,
authenticates, then steps through various re-directs until it gets to
the final stage and stops. I thought the certificate was supplying all
of my information so am a little confused by the final debug results
showing Basic authentication.
 
 
debug(0): About to connect() to redxfer.wellsfargo.com port 443
debug(0): Trying 209.84.206.42...
debug(0): connected
debug(0): Connected to redxfer.wellsfargo.com (209.84.206.42) port 443
debug(0): SSL re-using session ID
debug(0): SSLv3, TLS handshake, Client hello (1):
debug(0): SSLv3, TLS handshake, Server hello (2):
debug(0): SSLv3, TLS handshake, CERT (11):
debug(0): SSLv3, TLS handshake, Server key exchange (12):
debug(0): SSLv3, TLS handshake, Request CERT (13):
debug(0): SSLv3, TLS handshake, Server finished (14):
debug(0): SSLv3, TLS handshake, CERT (11):
debug(0): SSLv3, TLS handshake, Client key exchange (16):
debug(0): SSLv3, TLS change cipher, Client hello (1):
debug(0): SSLv3, TLS handshake, Finished (20):
debug(0): SSLv3, TLS change cipher, Client hello (1):
debug(0): SSLv3, TLS handshake, Finished (20):
debug(0): SSL connection using EDH-RSA-DES-CBC3-SHA
debug(0): Server certificate:
debug(0): subject: /CN=redxfer.wellsfargo.com
debug(0): start date: yyyy-mm-dd hh:mm:ss GMT
debug(0): expire date: yyyy-mm-dd hh:mm:ss GMT
debug(0): issuer: /C=US/O=RSA Data Security, Inc./OU=Secure Server
Certification Authority
debug(0): SSL certificate verify result: error number 1 (19), continuing
anyway.
debug(2): GET / HTTP/1.1
--passed/returned each time according to debug info.....
User-Agent: PycURL/7.13.2
Host: redxfer.wellsfargo.com
Pragma: no-cache
Accept: */*
Cookie: FDX=random cookie stuff
 
 
debug(1): HTTP/1.1 302 Found
debug(1): Date: Wed, 25 May 2005 20:48:29 GMT
debug(1): Server: Apache/1.3.12 (Unix) mod_ssl/2.6.6 OpenSSL/0.9.6
SecureTransportWWW/3.0.5
debug(0): Replaced cookie FDX="random" for domain
redxfer.wellsfargo.com, path /, expire 0
debug(1): Set-Cookie: FDX=random; path=/
debug(1): Location:
https://redxfer.wellsfargo.com:443/?&STCO=1QpTknZ8lI-cAADm4goE&STCOEND
debug(1): Transfer-Encoding: chunked
debug(1): Content-Type: text/html; charset=iso-8859-1
debug(0): Ignoring the response-body
debug(0): Connection #0 to host redxfer.wellsfargo.com left intact
debug(0): Issue another request to this URL:
'https://redxfer.wellsfargo.com:443/?&STCO=1random&STCOEND'
debug(0): Re-using existing connection! (#0) with host
redxfer.wellsfargo.com
debug(0): Connected to redxfer.wellsfargo.com (209.84.206.42) port 443
debug(2): GET /?&STCO=1random&STCOEND HTTP/1.1
    --Only difference is that the Cookie: changes here (looks like it
does it in the Replaced line above...)
 
debug(1): HTTP/1.1 302 Found
debug(1): Date: Wed, 25 May 2005 20:48:30 GMT
debug(1): Server: Apache/1.3.12 (Unix) mod_ssl/2.6.6 OpenSSL/0.9.6
SecureTransportWWW/3.0.5
debug(0): Replaced cookie FDX="random" for domain
redxfer.wellsfargo.com, path /, expire 0
debug(1): Set-Cookie: FDX=random; path=/
debug(1): Location:
https://redxfer.wellsfargo.com/?&STCO=2random&STCOEND
debug(1): Transfer-Encoding: chunked
debug(1): Content-Type: text/html; charset=iso-8859-1
debug(0): Ignoring the response-body
debug(0): Connection #0 to host redxfer.wellsfargo.com left intact
debug(0): Issue another request to this URL:
'https://redxfer.wellsfargo.com/?&STCO=2random&STCOEND'
debug(0): Re-using existing connection! (#0) with host
redxfer.wellsfargo.com
debug(0): Connected to redxfer.wellsfargo.com (209.84.206.42) port 443
debug(2): GET /?&STCO=2random&STCOEND HTTP/1.1
 
debug(1): HTTP/1.1 302 Found
debug(1): Date: Wed, 25 May 2005 20:48:30 GMT
debug(1): Server: Apache/1.3.12 (Unix) mod_ssl/2.6.6 OpenSSL/0.9.6
SecureTransportWWW/3.0.5
debug(0): Replaced cookie FDX="random" for domain
redxfer.wellsfargo.com, path /, expire 0
debug(1): Set-Cookie: FDX=random; path=/
debug(1): Location: https://redxfer.wellsfargo.com/
<https://redxfer.wellsfargo.com/>
debug(1): Transfer-Encoding: chunked
debug(1): Content-Type: text/html; charset=iso-8859-1
debug(0): Ignoring the response-body
debug(0): Connection #0 to host redxfer.wellsfargo.com left intact
debug(0): Issue another request to this URL:
'https://redxfer.wellsfargo.com/'
debug(0): Re-using existing connection! (#0) with host
redxfer.wellsfargo.com
debug(0): Connected to redxfer.wellsfargo.com (209.84.206.42) port 443
debug(2): GET / HTTP/1.1

debug(1): HTTP/1.1 401 Authorization Required
debug(1): Date: Wed, 25 May 2005 20:48:30 GMT
debug(1): Server: Apache/1.3.12 (Unix) mod_ssl/2.6.6 OpenSSL/0.9.6
SecureTransportWWW/3.0.5
debug(1): WWW-Authenticate: Basic realm="FileDriveWWW"
debug(1): Transfer-Encoding: chunked
debug(1): Content-Type: text/html; charset=iso-8859-1
debug(0): Connection #0 to host redxfer.wellsfargo.com left intact
 
Final Results:
 
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>401 Authorization Required</TITLE>
</HEAD><BODY>\n<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>
</BODY></HTML>
Peter A. Schott
drive financial services
Database Administrator
p: 214.237.3567
c: 214.734.1792
f: 214.237.3495
email: pschott_at_drivefinancial.com <mailto:pschott_at_drivefinancial.com>

 

___________________________________________________________________________________
This e-mail is covered by the Electronic Communications Privacy Act, 18 U.S.C.
Sections 2510-2521. The information contained in this e-mail is confidential
and intended only for use of the individual or entity named above. If the reader
of this message is not the intended recipient, or the employee or agent
responsible to deliver it to the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this message in error or there are any problems
please notify the originator immediately.

The unauthorized use, disclosure, copying or alteration of this message is
strictly forbidden. This mail and any attachments have been scanned for viruses
prior to leaving the Drive Financial Services network. Drive Financial Services
will not be liable for direct, special, indirect or consequential damages arising
from alteration of the contents of this message by a third party or as a result of
any virus being passed on.
___________________________________________________________________________________

_______________________________________________
http://cool.haxx.se/mailman/listinfo/curl-and-python
Received on 2005-05-25