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

Clarify use of CURLOPT_RANGE on upload #3814

jay opened this issue Apr 30, 2019 · 3 comments


Copy link

@jay jay commented Apr 30, 2019

I did this

Christopher Head (@Hawk777) reported on the mailing list that CURLOPT_RANGE does not work properly for ranged PUTs. I replied saying PUT is only for complete replacement of a resource, not partial. He replied saying Amazon allows ranged PUTs (doc).

I expected the following

The documentation does not specify the behavior of CURLOPT_RANGE on upload, so we should clarify that and in doing so decide whether or not what was reported is a bug (I think it's not since it's against the RFC).


This comment has been minimized.

Copy link

@bagder bagder commented May 3, 2019

curl has an approach to resumed uploads with PUT, even though it isn't encouraged nor specified in the RFC. It has however existed for a long time so we don't want to break it either.

For example, test 1001 and 1041 verify the existing functionality.


This comment has been minimized.

Copy link
Member Author

@jay jay commented May 16, 2019

What do you think about changing the doc to link to caution against using CURLOPT_RANGE for PUT uploads?

See my final analysis at in the reply quoted and current


This comment has been minimized.

Copy link

@bagder bagder commented May 16, 2019

Absolutely, propose a change if you can come up with wording you think will help users!

@curl curl deleted a comment from Simonair99 Jun 12, 2019
@jay jay closed this in 28f6fda Jul 17, 2019
caraitto added a commit to caraitto/curl that referenced this issue Jul 23, 2019
AFAICT CURLOPT_RANGE does not support ranged HTTP PUT uploads so I've
cautioned against using it for that purpose and included a workaround.

Reported-by: Christopher Head

Closes curl#3814
@lock lock bot locked as resolved and limited conversation to collaborators Oct 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.