Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Using --etag-compare with --output truncate existing output #5181
I did this
If we try to update
I would like to help resolve this issue, but I am having a hard writing a test case of this.
I would need the ability to specify existing files like
Is there some documentation on the language used for the test cases?
You can create files for the test in
Yes tests/FILEFORMAT but I will also recommend grepping existing test cases in case the language in the docs isn't clear!
Using the --etag-compare option, we can ask the server to either send the file if it was updated or respond with a 304 response code to signify that the file did not change. This commit recognize this response code and avoid writing the output file, which avoid truncating a previously downloaded file. This fix issue #5181.