New submission from Wiktor Niesiobedzki:
It looks like, when doing PUT together with a file-like object to send,
http.client will try to send the whole file before analysing the response from
the server.
If you do the following:
$ dd if=/dev/zero of=/tmp/300mb.zero bs=1M count=300
And then run following code in Python 3.4 (tested 3.4.3 on Linux and FreeBSD):
import http.client
conn = http.client.HTTPSConnection('api.onedrive.com')
req = conn.request(
method='PUT',
url='https://api.onedrive.com/v1.0/drives/me/root:/test.file:/content',
body=open("/tmp/300mb.zero", "rb"))
resp = conn.getresponse()
You'll notice the hang. After some time, it will aborted with BrokenPipeError:
[Errno 32] Broken pipe. If you run the following code within pdb debugger, and
interrupt, you'll probably interrupt somewhere within write loop. You can call
self.read() and see, that HTTP 413 is waiting to be interpreted.
Doing similar action with curl:
$ $ curl -v -T /tmp/300mb.zero
https://api.onedrive.com/v1.0/drives/me/root:/test.file:/content
Gives you immediate HTTP 413 error. Can we have the same behaviour in
http.client library?
----------
components: IO
messages: 256808
nosy: Wiktor Niesiobedzki
priority: normal
severity: normal
status: open
title: htp.client PUT method ignores error responses sent immediatly after
headers
type: behavior
versions: Python 3.4
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25919>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
