Send an upload to a server using HTTP/2 without the size set before-hand. (If the size is set, it is limited to 64bit.) due to the logic that still decreases the "upload left" counter even when the size is unknown, it may reach zero accidentally after 2^64 bytes have been transferred even if the transfer hasn't actually ended.
I expected the following
curl should allow the upload stream to go on forever.
curl/libcurl version
all
operating system
all
Note: I have a patch in progress for this already, but I'm holding it off until after the pending release to give it more time to mature.
The text was updated successfully, but these errors were encountered:
I'm sure you're technically correct but are you saying there's a use case for over 16 exabytes? When I've touched http2.c I've never accounted for that...
Maybe, maybe not. It just struck me that the solution I went with has this limitation and it is easy to fix so I figured it is still worth it. I can imagine use cases where you for example stream video or something in a virtually never-ending stream.
I did this
Send an upload to a server using HTTP/2 without the size set before-hand. (If the size is set, it is limited to 64bit.) due to the logic that still decreases the "upload left" counter even when the size is unknown, it may reach zero accidentally after 2^64 bytes have been transferred even if the transfer hasn't actually ended.
I expected the following
curl should allow the upload stream to go on forever.
curl/libcurl version
all
operating system
all
Note: I have a patch in progress for this already, but I'm holding it off until after the pending release to give it more time to mature.
The text was updated successfully, but these errors were encountered: