[tahoe-lafs-trac-stream] [tahoe-lafs] #1679: Potential download regression 1.9.1 versus 1.8.3

[tahoe-lafs]

#1679: Potential download regression 1.9.1 versus 1.8.3
--------------------------+-----------------------
     Reporter:  nejucomo  |      Owner:  nobody
         Type:  defect    |     Status:  new
     Priority:  major     |  Milestone:  undecided
    Component:  unknown   |    Version:  1.9.1
   Resolution:            |   Keywords:
Launchpad Bug:            |
--------------------------+-----------------------

Comment (by nejucomo):

 Some more details:

 The functioning lafs client (v 1.8.3) lives behind a public proxy:

 https://con.struc.tv/uri/URI:DIR2-RO:7qyqs2kopmglnstoquia4stxta:iz5jmy5cq34spq5h47my55mmb4uucfolbnfb6lxxe545su26cgta/index.html

 -you can poke at that if interested.

 By using curl against the malfunctioning client (v 1.9.1) to the same URL
 path, I get the {{{NoSharesError}}}.  However, I *can* successfully make a
 request to the containing directory
 {{{/uri/URI:DIR2-RO:7qyqs2kopmglnstoquia4stxta:iz5jmy5cq34spq5h47my55mmb4uucfolbnfb6lxxe545su26cgta/}}}
 - so I made a {{{t=json}}} request on the directory to find the file's
 capability, and make another curl request to that, which also fails in the
 same manner.

 *Importantly*, the public gateway (v 1.8.3) also results in the same error
 when the request is made by capability.  Example:

 https://con.struc.tv/uri/URI:CHK:kqnb2i6tufbyrou4klft7qn36y:5a6alvxpu2vsw45aiqfjriukxaoxno4har2hz2s2isczyppkuhja:1:1:64

 It appears the first request (through v 1.8.3) succeeds and the later
 (through 1.8.3) fails consistently.  Can anyone else verify this?

 Meanwhile, *both* requests fail against my 1.9.1 client.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1679#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage