[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2459: webapi doesn't handle Range header correctly

[Tahoe-LAFS]

#2459: webapi doesn't handle Range header correctly
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  daira
  spreitzer              |     Status:  assigned
         Type:  defect   |  Milestone:  1.10.2
     Priority:  major    |    Version:  1.10.0
    Component:  code-    |   Keywords:  webapi reliability availability
  frontend-web           |  mutable retrieve Range http standards
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by Brian Warner <warner@…>):

 In [changeset:"89e9076c41420a4145ae9a1db236dc2a1eb41259/trunk"]:
 {{{
 #!CommitTicketReference repository="trunk"
 revision="89e9076c41420a4145ae9a1db236dc2a1eb41259"
 mutable/retrieve.py: rewrite partial-read handling

 This should tolerate offset/size combinations that read the last byte of
 the file, something which was broken before. It quits early in the case
 of zero-byte reads, to simplify the resulting "which segments do I need"
 logic. Probably addresses ticket:2459.
 }}}

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2459#comment:8>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage