Sesame shouldn't get the repository in the interceptor if the current request is a DELETE

Description

Currently when the user is trying to delete a repository with:

the repository is first initialized in the repository interceptor and then there is a "hack" to close the connection that was opened in RepositoryController's delete repository code.
The problem is that sometimes the sail implementation might throw on initialize and then there is no way for the user to delete the repository.

Environment

None

Assignee

Jeen Broekstra

Reporter

Nikola Petrov

Labels

None

Priority

Major
Configure