Ticket #573 (closed Defect: fixed)

Opened 11 years ago

Last modified 9 years ago

File Browser: revealing files/folder fails when not logged in

Reported by: jri Owned by: jri
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.1.2
Keywords: Cc: dgf, Malte, JuergeN
Complexity: 3 Area:
Module: deepamehta-files


Clicking on a File or Folder in the detail panel's Folder Content listing fails with 401 (Unauthorized) when not logged in.

While from the user's perspective browsing the filesystem looks like a read-only situation (and thus should be allowed for guest users), DM actually creates the File/Folder? topics on-the-fly while browsing. This is currently done via a POST request, which (in the default configuration) fails if not logged in.

This scenario is similar to creating Search topics, which from the user's perspective can be regarded as read-only situation as well. That's why we've decided searching (including creation the Search topic) is a GET request.

Note: normally search or browse actions are regarded as read-only, what is reflected by using a GET request. But due to the distinctiveness of the DM GUI things are actually *created* while searching or browsing.

Regarding the File Browser issue the consequence would be to realize the browse actions (reveal a File, reveal a Folder) as GET requests as well, despite things are actually created.

Should we do it this way?

Change History

comment:1 Changed 11 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 10 years ago by jri

  • Milestone Release 4.1.3 deleted

comment:3 Changed 9 years ago by Jörg Richter <jri@…>

In 2f8e0d44a6c4bdd2732f292ee953782344a5c131/deepamehta:

Fix: browse public file repos by anonymous (#573).

Anonymous can reveal public Folder topics and browse its contained files/folders.

Note: anonymous still can't create new file browsers as the Create menu is not available at all (except in Common workspaces, provided the write_requires_login flag is set to false). I regard this OK at the moment.

See #573.

comment:4 Changed 9 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.