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

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

Inizia riproducendo le richieste POST e PUT per /foo.txt con text/plain e text/turtle, insieme alla richiesta del contenitore per /foo.txt/. Poi esamina il comportamento correlato di GET e dei redirect; il lavoro è completo quando l'URL della risorsa e il comportamento dello slash finale sono definiti in modo coerente e vengono impedite risorse duplicate con la stessa URL.