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

Commencez par reproduire les requêtes POST et PUT pour /foo.txt avec text/plain et text/turtle, ainsi que la requête de conteneur pour /foo.txt/. Examinez ensuite le comportement associé de GET et des redirections ; le travail est terminé lorsque l’URL de la ressource et le comportement du slash final sont définis de manière cohérente et que les ressources en double avec la même URL sont empêchées.