You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When client downloads new file with bytes=xxx- header in proxy mode, seed and peer will generate different taskids. Because there are different range fields in urlMeta. Then peer will failed in SyncPieceTasks with seed, which will lead to downloading from source.
The range in peer urlMeta is xxx- here.
But scheduler parses range with MaxInt64 as default size. The range here will be xxx-xxx
Expected behavior:
Seed and peer should generate the same taskid with bytes=xxx- http head and peer downloads file from seed.
How to reproduce it:
Download file with range bytes=xxx- in header.
Environment:
Dragonfly version: v2.1.6
OS:
Kernel (e.g. uname -a):
Others:
The text was updated successfully, but these errors were encountered:
Bug report:
When client downloads new file with
bytes=xxx-
header in proxy mode, seed and peer will generate different taskids. Because there are different range fields in urlMeta. Then peer will failed inSyncPieceTasks
with seed, which will lead to downloading from source.The range in peer urlMeta is
xxx-
here.But scheduler parses range with MaxInt64 as default size. The range here will be
xxx-xxx
Expected behavior:
Seed and peer should generate the same taskid with
bytes=xxx-
http head and peer downloads file from seed.How to reproduce it:
Download file with range
bytes=xxx-
in header.Environment:
uname -a
):The text was updated successfully, but these errors were encountered: