Dmitri Bourlatchkov

Currently Namespaces fall under the same authZ checks as any other content object (tables, views, etc.)

#4773 could be used for deletes

> the key-list contains the state for all commits excluding the current one. Yes, this is not a correctness issue, but an optimization issue. My point is that we could...

However, when #4592 is implemented this issue will become a moot point.

> [...] to verify the key-list generated after the commit with the delete-op Here's the log: ``` Put: create-contents-2022-07-25-14-28-13.contents.0 Put: create-contents-2022-07-25-14-28-13.contents.0 Key list key: create-contents-2022-07-25-14-28-13.contents.0 Delete: create-contents-2022-07-25-14-28-13.contents.0 Key list key:...

Conversely, `NessieNotAuthorizedException` represents HTTP 401 errors, but exists outside of the `http` client scope in code... Some clarification seems to be in order there,

Is the description still up-to-date? This link in particular seems to be broken: https://github.com/snazy/nessie-integration-tests/

I _guess_ this is not related to the REST API rework. I believe all auth stuff is rather independent of actual REST parameters. This is more of a client thing,...

Another point: Even though using `%2F` in the URL path currently works, it is inconvenient for programmatic use because tools (e.g. `rest-assured`) will generally re-escape the `%` if it is...

@tmnd1991 : by "mock" do you mean something available in test or in an actual (deployed) Nessie server? In any case, if there are no security concerns a property-bases user...