This means I want to structure my request header with "Connection: keep alive"
for the server which support connect alive,
But I checked the requeset header send by myself, the connection still closed,
no affect by set
And I also found this in python document:
==============================
urllib.request.urlopen(url, data=None, [timeout, ]*, cafile=None, capath=None,
cadefault=False, context=None)
Open the URL url, which can be either a string or a Request object.
data must be an object specifying additional data to be sent to the server, or
None if no such data is needed. See Request for details.
urllib.request module uses HTTP/1.1 and includes Connection:close header in its
HTTP requests.
===============================
Does it mean urllib.request don't support 'keep alive'?
Thanks
在 2020-08-18 04:51:03，"Barry" <ba...@barrys-emacs.org> 写道：
>
>
>> On 17 Aug 2020, at 18:23, xuanwu348 <xuanwu...@163.com> wrote:
>>
>> hi everyone
>>
>>
>> Good day, the code as below, I try to make a long connection by set the
>> connection to "keep-alive", but actually it's not as expected. Why? Thanks
>
>What this means is. Please web server keep the connect alive if you can.
>The web server is allowed to close the connection if it wants too.
>
>Barry
>
>>
>>
>> import urllib.request as req
>> headers = {"authorization": "Bearer {}".format(self.token),
>> "Content-Type": "multipart/form-data;
>> boundary={}".format(self.boundary),
>> "Connection": "keep-alive"}
>> request = req.Request(event_uri, headers=headers, data=data.encode("utf-8"))
>>
>>
>>
>>
>>
>> Accept-Encoding: identity
>>
>> Content-Length: 705
>>
>> Host: 10.10.1.114:9443
>>
>> User-Agent: Python-urllib/3.8
>>
>> Authorization: Bearer a1.BUiPZxxxxxxxxxxxxxxxxxxCQdH2c9uegml
>>
>> Content-Type: multipart/form-data; boundary=--testtest--
>>
>> Connection: close
>>
>>
>>
>>
>>
>>
>>
>> Best Regards
>> --
>> https://mail.python.org/mailman/listinfo/python-list
>>
--
https://mail.python.org/mailman/listinfo/python-list
