Support the `If-None-Match` header

Expected behaviour

• POST a resource to an IRI where a resource already exists, with the If-None-Match header set.
• The server returns 412, and the original resource is unchanged.

Actual behaviour

• POST a resource to an IRI where a resource already exists, with the If-None-Match header set.
• The server returns 201 Created, and the original resource is overwritten.

Additional context

When receiving a resource creation request (i.e. POST or PUT, possibly PATCH?), if the If-None-Match header is set, the server should perform a check to ensure that no resource is already stored at the target IRI.

In the case of POST, since the Slug header is meant to be a hint and not a hard constraint, I'm not sure what the behaviour should be, but when PUTting a resource to an IRI where a resource already exists, an If-None-Match request should fail with 412.

Open question

When only having write (but not read) access to a container, can this be used to exfiltrate information one should not be allowed to access ?

Aucun fichier, test ou point d’entrée n’est indiqué. Commencez par localiser le traitement des requêtes POST et PUT du serveur ainsi que le traitement des en-têtes conditionnels, puis examinez le comportement existant autour de If-None-Match. La tâche est terminée lorsque le comportement demandé 412/no-overwrite est couvert et que les questions concernant POST/Slug et l’accès en écriture seule sont résolues.