When a resource has a property made of a URI pointing to a resource managed by the same repository and containing a hash fragment, if the destination resource is deleted, the first resource is not accessible (404) except with HEAD, and the tombstone of the deleted resource is not deletable.
E.g. </a> ex:link </a/b#c>
Deleting /a/b causes /a to become inaccessible.
Attached is a shell script that reproduces this behavior. Tested behind Apache rev proxy.
This is a critical issue since Hydra/Curation Concerns deletes resources in a way that causes this scenario.