nodeSolidServer / nodeSolidServer/node-solid-server

POST/PUT in NSS allow multiple resource with same url and different content-type

Open
#1,529 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

You can create resources :

  1. https://pod/foo.txt with content-type text/plain => creates file : /foo.txt
  2. https://pod/foo.txt with content-type text/turtle => creates file /foo.txt$.ttl
  3. https://pod/foo.txt/ as a container => creates folder /foo.txt

The first 2 have the same url and there are 2 different files created.
All 3 have the same visual representation in SolidOs.

The first 2 should not occur and I think this is a bug
For the third one I remember @timbl writing it should not occur, but did not find where.
There was also a redirect discussion between foo/bar/ and foo/bar. His this something to do in GET ?

Is there any solid/specification, I did not find anything ? @csarven @michielbdejong

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the POST and PUT requests for /foo.txt with text/plain and text/turtle, plus the container request for /foo.txt/. Then inspect the related GET and redirect behavior; done means the resource URL and trailing-slash behavior are defined consistently and duplicate resources with the same URL are prevented.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.