-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix read chunks #291
Fix read chunks #291
Conversation
Hi, thanks for your contribution and sorry for the slow response. |
Hi, no problem. No, I only tested it with python PS: By the way I believe that the issue #282 is linked with this one. |
Hi, |
Hi, |
The previous code addressed existing problems and was configurable with Before we can merge, we need to make sure that the change does not introduce a regression.
If we decide to merge, we also need to remove the hot fix flag and add |
Ok thanks, so I tested it with a windows environment but I am not able to test it with macOS Finder.
I also added the field to the deprecated list. |
Smoke test with Finder on macOS Ventura passed as well, thank you! |
Hi,
This PR aims to fix #290.
I dug in the code to identify the cause of the problem and here is what I understood.
The issue I identified in the code is that
wsgidav
add an extra layer of packet decoding above the wsgi layer used to run the server (cheroot, ...).wsgidav
should not try to decode chunks as they are already decoded and normalised by the wsgi server.I just changed the decoding for
stream_data_chunked
but we might also want to refactorstream_data
.@mar10 Let me know if you have any questions.