Skip to content

cargo build fails with HTTP parser error: success; class=Net (12) #10216

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

Closed
uglyoldbob opened this issue Dec 18, 2021 · 3 comments
Closed

cargo build fails with HTTP parser error: success; class=Net (12) #10216

uglyoldbob opened this issue Dec 18, 2021 · 3 comments
Labels
C-bug Category: bug

Comments

@uglyoldbob
Copy link

Problem

I am running cargo build and am encountering an odd failure.

$ cargo build
Updating crates.io index
warning: spurious network error (2 tries remaining): HTTP parser error: success; class=Net (12)
warning: spurious network error (1 tries remaining): HTTP parser error: success; class=Net (12)
error: failed to fetch https://github.com/rust-lang/crates.io-index

Caused by:
HTTP parser error: success; class=Net (12)

I am running debian 10, 4.19.0-18-686-pae #1 SMP Debian 4.19.208-1 (2021-09-29) i686 GNU/Linux

Not really sure what to do since it says "error: success".

Steps

No response

Possible Solution(s)

No response

Notes

No response

Version

cargo 1.42.1
release: 1.42.1
@uglyoldbob uglyoldbob added the C-bug Category: bug label Dec 18, 2021
@ehuss
Copy link
Contributor

ehuss commented Dec 19, 2021

cargo 1.42.1

This version is quite old, would you be able to use a newer version? The latest release is 1.57.

@uglyoldbob
Copy link
Author

I upgraded to debian testing, which has cargo 1.56.0. This solved my problem.

@ehuss
Copy link
Contributor

ehuss commented Dec 19, 2021

Sounds good, I'm going to close this out as fixed.

@ehuss ehuss closed this as completed Dec 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bug
Projects
None yet
Development

No branches or pull requests

2 participants