Support the `If-None-Match` header

No se nombran archivos, pruebas ni puntos de entrada. Empieza por localizar el manejo de solicitudes POST y PUT del servidor y el procesamiento de encabezados condicionales; después, revisa el comportamiento existente en torno a If-None-Match. La tarea estará terminada cuando el comportamiento solicitado de 412/no-overwrite esté cubierto y se hayan resuelto las cuestiones sobre POST/Slug y el acceso de solo escritura.

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 ?