1.1.0
Sync Gateway 1.1 packs in a number of significant enhancements, including:
- A new integration mechanism: Webhooks. With this release, we are beginning to expose an event model to which you can add handlers. This makes it even easier to integate Couchbase Mobile with line of business applications, 3rd party services and apps, etc.
- PouchDB compatibility. Extend your Couchbase Mobile user experience to your HTML5/JavaScript apps.
Cross-Origin Resource Sharing (CORS) support. Enable Sync Gateway to respond to HTTP requests that origin from one or more approved external websites. - Friendlier default configuration. Now when you run Sync Gateway without providing any configuration options, the Guest user will be enabled and will have access to all documents. The tradeoff, for security reasons, is that Sync Gateway will default to listening on the local loopback interface only.
- Production certification for Couchbase 3.1, and non-production certification for using 4.0 (Beta 1). Sync Gateway users are encouraged to upgrade to 3.1 in order to take advantage of all the great improvements since the 2.5.2 release.
Performance
Enhancements
- #859 Uptake TCP keep-alive support for go-couchbase
- #763 Improve view creation by Sync Gateway
- #708 Insecure mode on default sync_gateway bucket
- #482 Sync Gateway web hooks
- #457 Add additional platform support for service installation scripts
- #404 Moving from TAP to DCP
Bugs
- #880 Changes feed fails to backfill channel under heavy access() load
- #878 sg doesn't properly handle config files with buckets '%' in the name
- #852 webhooks events can't POST for HTTPS servers using self-signed cert
- #850 Logging doesn't always use the same unit
- #847 Installing sync gateway service fails
- #821 Session API does not honor the password parameter
- #812 webhooks: Not all events are getting POSTed
- #811 webhook: Not all revision ids are sent with webhook events.
- #810 Sync Gateway crashes while processing webhook events
- #809 Sync Gateway crashes while processing the changes feed
- #808 The revision Id passed in the Etag header should be enclosed in quotes
- #783 Windows line breaks in sync function cause SG to fail
- #775 SG handling for mutations deduplicated by Couchbase feed
- #762 configurable CORS on login resources
- #745 Ignores heartbeat parameter in _changes POST request
- #691 Bucket name with percent symbol is not handled correctly in config file
- #687 Windows: Pull replication doesn't work on :4984 (no documents or changes returned)
- #679 Webhook does not give warning or error when http server delay response pass the timeout value
- #661 Webhook filter with invalid event type or event handler does not result in error or warning to users
- #653 Sync Gateway not starting first time
- #628 DCP events not appearing on changes feed
- #621 Changes Feed repeats all the changes when a change is made
- #563 SG service installation, when using --runas, update all paths that point to user home
- #562 PUT /db should not return 405; causes client replicator to fail
- #544 Sync_gateway service installation result in two data directories when there is an inactive service
- #535 sync_gateway_service_install.sh should explicitly state that command-line arguments require an '=' before the value
- #530 Some of the service install script parameters should be removed
- #525 SG TAP timeout issue
- #521 Fail to start sync_gateway service
- #513 When stopping Sync_gateway service on Centos 6 process is left running
- #501 Revision pruning isn't effective when history includes conflicts (even when tombstoned)
- #491 Items in SG channel not reflected in change feed.
Where to get it
You can download this release from Couchbase.com
Requirements
Sync Gateway 1.1 is compatible with the following editions of Couchbase Server:
| Sync Gateway | Couchbase Server |
|---|---|
| 1.1 | 2.2.x |
| 1.1 | 2.5.x |
| 1.1 | 3.0.5 |
| 1.1 | 4.0 Beta 1 (though not supported for production use) |
Support Statement
Version 1.0 was released in May, 2014. With this release of version 1.1, the support window for 1.0 expires in December 2015.
| Release | Release Date | End of Life Date |
|---|---|---|
| 1.0 | May 2014 | June 2016 |
| 1.1 | June 2015 |