I did this
(lib)curl "supports" resumed uploads using POST/PUT since the dawn of time.
In HTTP land however, this is not interoperable and it has been agreed since a long time back that this does not work protocol wise. Trying the same command line on different servers will therefore have different outcomes, and no one will be happy.
Because of these problems, there should be few users relying on this hack. We should remove it.
There is a separate and recent effort to document a protocol compliant way to do resumed HTTP uploads and curl should probably support that, but that will need a different approach/option anyway.
I expected the following
curl should reject attempts to do HTTP resumed uploads.
curl/libcurl version
git master
operating system
independent
I did this
(lib)curl "supports" resumed uploads using POST/PUT since the dawn of time.
In HTTP land however, this is not interoperable and it has been agreed since a long time back that this does not work protocol wise. Trying the same command line on different servers will therefore have different outcomes, and no one will be happy.
Because of these problems, there should be few users relying on this hack. We should remove it.
There is a separate and recent effort to document a protocol compliant way to do resumed HTTP uploads and curl should probably support that, but that will need a different approach/option anyway.
I expected the following
curl should reject attempts to do HTTP resumed uploads.
curl/libcurl version
git master
operating system
independent