http and https

I have a use case where the couchdb server may be SSL protected (https port 6984). For generality, I'd like to probe both choices and use the successful one.

I tried opening 2 instances of nano, one for http and one for https but it seems that the first invocation sets some internal flags so the second one points to the first. Perhaps cookies?

This is on current version of couchdb and nano. (a fresh install).

In general, either 2 separate couchdb connections should be possible (and documented), or there should be a way to close and reopen with fresh address.

No files or tests are named. Reproduce the two-instance HTTP/HTTPS case on a fresh Nano and inspect how connection addresses and internal state are initialized; done when separate connections work independently or a documented close-and-reopen path is provided.

Written by the indexing model from the issue text.