Jonathan Schweder added the comment:
Hello @tkruse, I have made some research and found that when using the Chunked
transfer encoding [1], each chunk is preceded by its size in bytes, something
that really happen if you check the content of one downloaded file from the
example you provided
Change by Jonathan Schweder :
--
keywords: +patch
nosy: +jaswdr
nosy_count: 1.0 -> 2.0
pull_requests: +25361
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/26775
___
Python tracker
<https://bugs.python.org/i
Jonathan Schweder added the comment:
Not exactly, in the RFC example they use a/b/c for the path, but when using
http:g there is no nested path, so it should be http:///g, no?
--
___
Python tracker
<https://bugs.python.org/issue40
Jonathan Schweder added the comment:
@op368 I don't think that this is a bug, [1] literally uses this exact example
and shows the expected behaviour.
[1] https://datatracker.ietf.org/doc/html/rfc3986#section-5.4.2
--
nosy: +jaswdr
___
P
Jonathan Schweder added the comment:
@demonia you are more than welcome to send a PR, sent it and add a reference to
this issue, so it could be reviewed.
--
nosy: +jaswdr
___
Python tracker
<https://bugs.python.org/issue43
Jonathan Schweder added the comment:
Simple example to reproduce the issue:
from http import cookies
C = cookies.SimpleCookie()
C["ys-api/mpegts/service"] = "blabla"
print(C.output())
@ra1nb0w so far as I have found [1][2], the "/" not a valid character for the
Jonathan Schweder added the comment:
@ueJone according to the
(RFC)[https://datatracker.ietf.org/doc/html/rfc6455#section-1.4] the FIN/ACK is
not normative, in other words is recommended but not required, I've checked the
syscalls of the server, see it below:
```
...
1561 15143 wr
Change by Jonathan Schweder :
--
keywords: +patch
pull_requests: +24563
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/25889
___
Python tracker
<https://bugs.python.org/issu
Jonathan Schweder added the comment:
@jcolo
Awesome to hear that you were able to run the example, in fact I got in the
same trap, thinking the same that the example should carry the server and
client side, I guess we can improve the documentation to avoid it, I'll sent a
PR to mak
Jonathan Schweder added the comment:
I was able to execute the example in Debian 10 + Python 3.10+
Did you execute the server too? You need to create two files, one for the
client code and one for the server code, the server as specified by the example
should be something like the code
Jonathan Schweder added the comment:
@kormang this is an expected behaviour, this is a problem even for the OS
level, just because it is impossible to know when the reader needs to stop
waiting, the best option here is to implement some timeout mechanism.
--
nosy: +jaswdr
Jonathan Schweder added the comment:
a.niederbuehl tasks are free of context, meaning that the task does not know
what was done inside it, and by consequence is impossible to know when or not
release a lock. This is by design and normally in these cases you need to be
aware of the lock, by
12 matches
Mail list logo