I have an app that makes a https POST to a remote server that I have no
control over. The app runs fine in python 2.1.3 with socket.ssl
compiled with openssl-0.9.6, however it will not run in python 2.3.3
compiled with openssl-0.9.7d. The script below demonstrates the problem.
path = "/cmaonline.nsf/ePayForm?OpenForm"
'''Desc=&Bank=National&email=&creditcardholdername =fgfgg&creditcardtype=VISA&creditcardnumber=455701 3000314262&ReturnHTTP=%2A&SendeMail=No&UID=0407151 706104&MultiBank=No&FinalPrice=35.00&MerchantID=36 &CompanyName=Bizar+Software&Mode=Test&Platform=Pla inText&__Click=0&ABN=ABN+xx+xxx+xxx+xxx&Returnemai l=&creditcardexpiryyear=2004&CVV=&Name=fgfgg&reade rs=MEL0036&creditcardexpirymonth=7&Principal='''
h = httplib.HTTPSConnection("merchant.ematters.com.au" , 443)
h.request('POST', path, body)
resp = h.getresponse()
f = resp.fp
resp = resp.read()
With python 2.1, the server accepts the request correctly and has a
However, with python 2.3 I get:
<H1>Error 500</H1>HTTP Web Server: Invalid POST Request Exception</BODY>
The debuglevel printouts show that python2.1 sends the request and
headers one at a time, where as python 2.3 sends the request and all the
headers at once, although the actual data send is identical, so I don't
see this as the problem. I actually hacked httplib in my python 2.3
installion to get _output() to send immediately rather than buffer, so
that the debug output is identical to the python2.1 output, and that
gives me a different error:
request -- HOST header was not sent</BODY></HTML>
So I am suspicious that the debug output is not showing what is actually
sent? I am really tearing my hair out with this problem because I really
need this app to work with pyton 2.3.3, and I cannot see what else it is
doing differently to cause this problem.
Are there any httplib/socket/ssl gurus out there that have any suggestions?
|All times are GMT. The time now is 07:14 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.