New submission from George Stephanos <gaf.stepha...@gmail.com>: When trying to POST /anything/ @ https://grooveshark.com/, I get an httplib.BadStatusLine exception (server returns nothing at all. It's a timeout since it waits a while).
The many Grooveshark webclients however works perfectly, along with a curl command (run through cygwin, commented out in the script) that does the exact same. Meaning this weird behavior is exclusive to Python. This issue was found to be present on many Windows systems. However, not all (all the systems have Python 2.7.2). I'm not sure what the difference is, and I'm not sure if this is a Python bug, but this is the only place I could think of to discuss the behavior. The only Linux system I've tested this on worked (again, Python 2.7.2). Note: If it fails on one system, it never succeeds no matter how much you try. The code *used* to work yesterday and it's been working for many months. Grooveshark might have changed something but this doesn't make any sense since curl works. Please try to reproduce this. I can provide any testing details needed. A script containing the code to test with is attached, along with the curl line and a BadStatusLine traceback. Excuse my complete ignorance on the inner workings of SSL and my weak English skills (second language). ---------- components: Windows files: ssltest.py messages: 162947 nosy: jtr51 priority: normal severity: normal status: open title: [httplib] httplib.BadStatusLine on any HTTPS connection in certain unknown cases. type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file26024/ssltest.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15082> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
