search

alexcrichton / curl-rust

Rust bindings to libcurl
MIT License
1.02k stars 233 forks source link

Possible bug in `read_function`? #179

Open sgrif opened 7 years ago

sgrif commented 7 years ago

I was attempting to debug why https://github.com/rust-lang/crates.io/blob/120f8008fb08c21fc6cd239c1100692a0ff487e6/src/tests/record.rs#L310-L370 was returning "Problem's parsing json". Changing the URL to http and then inspecting the traffic w/ wireshark, it looks like the request body is never being sent. https://github.com/rust-lang/crates.io/blob/120f8008fb08c21fc6cd239c1100692a0ff487e6/src/tests/record.rs#L347-L349 is definitely being called, and the buffer passed in is being populated correctly. I'm not sure if this is a bug in crates.io or a bug in curl-rust.

sgrif commented 7 years ago

In case it's relevant:

[master][~/builds/crates.io] curl --version
curl 7.43.0 (x86_64-apple-darwin14.0) libcurl/7.43.0 SecureTransport zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz UnixSockets
alexcrichton commented 7 years ago

I think this may have to do with something liek Expect: 100-continue or something like that, does that sound familiar though?