Menu

#1088 curl http resume doesn't interpret 416 correctly

closed
http (206)
5
2013-06-21
2012-02-02
No

This is inducable in 7.24.0; following commands replicate it.

rm linux-3.2.2.tar.bz2
curl --output linux-3.2.2.tar.bz2 http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.2.2.tar.bz2 && \
curl --output linux-3.2.2.tar.bz2 http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.2.2.tar.bz2 -C -

The returned headers are 416; specifically, the file is completed. Curl however does not handle it correctly, instead assuming resume isn't possible.

Discussion

  • Daniel Stenberg

    Daniel Stenberg - 2012-02-16

    I don't understand. Can you please add the exact headers this server returns for the command lines you run to illustrate how curl does it wrong? 416 is quite explicitly about when the range request cannot be satisfied.

     
  • Daniel Stenberg

    Daniel Stenberg - 2012-02-19
    • status: open --> pending
     
  • Daniel Stenberg

    Daniel Stenberg - 2012-02-19

    Thanks for reporting this issue and helping us improve curl and libcurl.

    We're awaiting feedback in this issue. Due to this, I have set the state of this issue to pending and it will automatically get closed later on unless we get further info.

    Please consider answering the outstanding questions or providing the missing info so that we can proceed to resolve this issue!

     
  • Daniel Stenberg

    Daniel Stenberg - 2012-05-06
    • status: pending --> closed
     
MongoDB Logo MongoDB