What steps will reproduce the problem?
1. make a request to pywebdav for a file
2.
3.
What is the expected output? What do you see instead?
1) If the request is HTTP/1.1, and chunked transfer encoding is used in the
response, I expect an HTTP/1.1 response, as indicated by the status line.
Currently, it seems that if a HTTP/1.1 request is made, pywebdav responds with
an HTTP/1.0 response that uses chunked transfer encoding. I believe this
response should be HTTP/1.1, as that's what the request was, and chunked
transfer encoding is part of HTTP/1.1, not HTTP/1.0.
What version of the product are you using? On what operating system?
0.9.8 on Ubuntu 14.04
Please provide any additional information below.
I can fix the problem by turning off chunked encoding. I noticed the issue
since a program I am using that connects to a webdav server was having an issue
since it wasn't decoding the chunked data. It uses Firefox/XULRunner. I suppose
that it sees a HTTP/1.0 response from pywebdav, and doesn't make any attempt to
decode the data, since Transfer-Encoding is not defined for HTTP/1.0 AFAIK.
Original issue reported on code.google.com by DStei...@gmail.com on 28 Sep 2014 at 7:03
Original issue reported on code.google.com by
DStei...@gmail.comon 28 Sep 2014 at 7:03