[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 daira):

 Replying to [comment:11 warner]:
 > Actually, I'm ok with not adding a test. The `test_mutable.py` tests
 exercise the `IReadable.read()` offset/range arguments pretty well, and I
 don't think we've observed any problems in the HTTP Range header parser.
 Would anyone object if I closed this?

 I'm ok with not adding a specific test of the HTTP layer, given that we
 already smoke-tested that, and the bug wasn't in that layer.

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