1.0.3, October 29, 2014
In 1.0.3 we have begun to reduce friction in the Sync Gateway's usability. We've added install scripts to expedite the installation of Sync Gateway as a service on Ubuntu and RedHat, made preventative measures against the POODLE vulnerability by disallowing SSLv3 connections, and improved the overall session management for custom authentication integration. Below is a highlight of issues fixed, and enhancements added:
- Fixed issue where a channel assigned to non existent user in sync function, would not get assigned when user was later added.
- Fixed issue where a bulk_docs request contains a document that alters channel access for the user making the request and the change doesn't take effect until after the request completes.
- Fixed issue where getting doc with
atts_since, might return data from a previous call.
- Fixed issue where existing documents assigned to a channel are not synced to a user that is assigned access to that channel at a later time
/dbnow respects an incoming
_idproperty, such that the value is used as the doc id rather than a UUID
- Set an expiration time for obsolete revisions to support automatic cleanup
- Ensure only active channels are returned in
_all_docsnow supports limit, startkey and endkey arguments
- Improved session management via Admin API for DELETE and GET
- Added support for setting custom read/write timeouts on HTTP(S) server
Our new install script support the installation of Sync Gateway as a service on the following platforms:
- Ubuntu 10.04, 32- and 64-bit
- Ubuntu 12.04, 32- and 64-bit
- Ubuntu 14.04, 32- and 64-bit
- Centos 5, 32- and 64-bit
- Centos 6, 32- and 64-bit
You can manually install Sync Gateway as a service onto Centos 7. Support for Centos 7 in our automated installation scripts will be coming soon.