We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally posted by @tlvince as https://github.com/eHealthAfrica/couchdb-bootstrap/issues/28, reposted here for convenience:
If you pass in a nano config as the url, e.g. to set requestDefaults (#14):
requestDefaults
bootstrap({ url: 'http://localhost:5984', requestDefaults: { auth: { user: 'admin', pass: 'admin' } } }, 'path/to/fs', cb)
… requestDefaults is lost after nano.use, for example in secure:
nano.use
// ... var dbname = utils.mapDbName(filename, options) var db = couch.use(dbname) console.log('couch: ', couch.config, '\ndb: ', db.config) // => // couch: { url: 'http://localhost:5984', // requestDefaults: { jar: false, auth: { user: 'admin', pass: 'admin' } }, // defaultHeaders: { 'X-Couch-Full-Commit': 'true' } } // db: { url: 'http://localhost:5984', db: '_users' }
In this case, this will cause subsequent requests to 401 (You are not authorized to access this db.).
You are not authorized to access this db.
Perhaps this is an issue with nano itself (apache/nano#278)?
The text was updated successfully, but these errors were encountered:
chore(test): test preserve requestDefaults
d97cec7
For #6
Thats long ago, please reopen if still an issue
Sorry, something went wrong.
No branches or pull requests
Originally posted by @tlvince as https://github.com/eHealthAfrica/couchdb-bootstrap/issues/28, reposted here for convenience:
If you pass in a nano config as the url, e.g. to set
requestDefaults
(#14):…
requestDefaults
is lost afternano.use
, for example in secure:In this case, this will cause subsequent requests to 401 (
You are not authorized to access this db.
).Perhaps this is an issue with nano itself (apache/nano#278)?
The text was updated successfully, but these errors were encountered: