-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/_{db}/_ensure_full_commit returns success for non-existent databases #1585
Comments
Any attempts to access Port 6004 is unusual, can you confirm this is the standard clustered (port 5984) port and not the node-local (port 5986) port? |
Yes, sorry, 6004 is mapped to 5984 on my docker container (the unusual port mapping is to accommodate multiple versions of CouchDB running). |
@flimzy thank you for reporting. This is a result of refactoring where previously the calls to a non-existent database were intercepted up the chain by auxiliary security check. I've opened PR #1588 to address this issue. By the way, I don't know if you aware, but in 2.x a call to |
I wasn't aware. It looks like this needs to be updated in the documentation. I'll try to find time to do that soon, if nobody beats me to it. |
If I attempt to call the
_ensure_full_commit
endpoint for a database with a name beginning with the '_' character, I get (fake) success, rather than 404.Expected Behavior
I expect a 404, as I get for a db with a standard name. Example:
Current Behavior
Apparent success, even though the database
_foo
does not exist.Context
Observed on CouchDB 2.2.0, but not on 2.1.1 and older. Tested using Docker images.
The text was updated successfully, but these errors were encountered: