Skip to content
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

curling directories now returns curl: (36) failed to resume file:// transfer #6845

Closed
lukegb opened this issue Apr 3, 2021 · 0 comments
Closed

Comments

@lukegb
Copy link
Contributor

@lukegb lukegb commented Apr 3, 2021

I did this

curl file:///etc/

I got

curl: (36) failed to resume file:// transfer

I expected the following

An empty response.

curl/libcurl version

 curl -V
curl 7.76.0 (x86_64-pc-linux-gnu) libcurl/7.76.0 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.9 libssh2/1.9.0 nghttp2/1.41.0
Release-Date: 2021-03-31
Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp 
Features: alt-svc AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IPv6 Kerberos Largefile libz NTLM NTLM_WB SPNEGO SSL TLS-SRP UnixSockets

operating system

NixOS

Linux totoro 5.4.77 #1-NixOS SMP Tue Nov 10 20:13:20 UTC 2020 x86_64 GNU/Linux

Notes

Since 957bc18, curling a directory now causes an error because we have a length for the directory of -1, which is always less than the requested start of 0.

lukegb added a commit to lukegb/curl that referenced this issue Apr 3, 2021
Trying to GET a directory on *nix systems has historically just
succeeded and given an empty result.
@bagder bagder closed this in 6d930d7 Apr 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant