[ ] Added tests for code changes or test/build only changes
[ ] Updated the change log file (CHANGES.md) or test/build only changes
[ ] Completed the PR template below:
Description
It is common to prepare and open a session to connect to iterate with couchdb. However, when you open a session, not necessarly you iterating with the database, you could be executing some transformation job. If you leave the session idle, the server could kill you connection and if you try to use the connection, the client raise an protocol error. See issue 461
Fixes #461
Approach
To avoid the ECONNRESET error you should open the connection with Connection: close header. This pr add a param that allow the user handle if he wants the default behavior, ie, keep alive true or not.
Checklist
CHANGES.md) or test/build only changesDescription
It is common to prepare and open a session to connect to iterate with couchdb. However, when you open a session, not necessarly you iterating with the database, you could be executing some transformation job. If you leave the session idle, the server could kill you connection and if you try to use the connection, the client raise an protocol error. See issue 461 Fixes #461
Approach
To avoid the ECONNRESET error you should open the connection with Connection: close header. This pr add a param that allow the user handle if he wants the default behavior, ie, keep alive true or not.
Schema & API Changes
Add param keep_alive to couchdb keep_alive
Security and Privacy
"No change"
Testing
Monitoring and Logging
"No change"