[tahoe-lafs-trac-stream] [tahoe-lafs] #1798: Segregate gateway HTTP ports: one for raw bytes and one for generated WUI pages

tahoe-lafs trac at tahoe-lafs.org
Sun Dec 15 11:52:11 UTC 2013


#1798: Segregate gateway HTTP ports: one for raw bytes and one for generated WUI
pages
----------------------------+----------------------------------------------
     Reporter:  davidsarah  |      Owner:  freddyb
         Type:  defect      |     Status:  new
     Priority:  major       |  Milestone:  soon
    Component:  code-       |    Version:  1.9.2
  frontend-web              |   Keywords:  wui same-origin security capleak
   Resolution:              |
Launchpad Bug:              |
----------------------------+----------------------------------------------

Comment (by freddyb):

 I'm not sure I fully understand. Do you mean three ports? WUI, Download
 and display? Why should download and display be separated?

 I thought about one port for download&display and one port for WUI and I
 realize that this might be much more work than anticipated, considering
 that I didn't think about the cli, which might need updating too.

 I think it could be useful to redirect (http 301 moved permantently) GET
 requests for files that accidentally go to the WUI port. This could
 benefit compatibility and help identifying code points that don't use the
 new port.

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


More information about the tahoe-lafs-trac-stream mailing list