https://bugs.documentfoundation.org/show_bug.cgi?id=152493

--- Comment #6 from László Németh <[email protected]> ---
(In reply to Mike Kaganski from comment #4)
> (In reply to Michael Stahl (allotropia) from comment #2)
> > "Transfer-Encoding: chunked" and libcurl cannot handle it.
> 
> I don't know how this may be related, but it seems that at least something
> is supported in libcurl:
> 
> https://pragmaticjoe.gitlab.io/posts/2016-09-04-http-chunked-encoding-using-
> c-and-libcurl/
> 
> which deals with more problematic case of not having all the data in
> advance, but also mentions that when everything is at hand, "you just need
> to add the header “Transfer-Encoding: chunked” to the request, and curl will
> take care of everything after that".

The ucb code contains several comments about Sharepoint and Nextcloud problems
with chunked encoding:

  // note: Sharepoint cannot handle "Transfer-Encoding: chunked"

  // note: Nextcloud 20 cannot handle "Transfer-Encoding: chunked"

etc.

Likely it's important, that a newer command line curl (e.g. on Ubuntu 22) has
got a similar problem with Vibe WebDAV server, i.e. it was possible to
overwrite *an existing remote file* only with --http1.0:

curl -u user:passwd --http1.0 -T local_modified_copy weblink

But an older curl (e.g. on Ubuntu 20.04: curl 7.68.0 (x86_64-pc-linux-gnu)
libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0
libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0
librtmp/2.3
Release-Date: 2020-01-08
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3
pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos
Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets) works with its
default options.

So switching on HTTP 1.0 as the common ground seems to be more viable solution
for me, than applying some low level settings, which would need more careful
testing likely with the different WebDAV servers.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to