> On Oct 31, 2014, at 1:21 AM, Thiago Alencar <[email protected]> wrote: > > - In the case of using a proxy in front of the sync gateway (e.g.: nginx), do > I need to specify "secure": NO to the CBLReplication's setCookie method, or > is a https:// url is enough?
This doesn't have anything to do with using a proxy. The 'secure' flag is the same as the 'secure' property of a cookie itself (as defined by whatever RFC.) It specifies that the cookie should only be sent over a secure connection (SSL/TLS). So its only effect would be if you set secure:YES but used an http: URL, in which case the cookie would not be sent. We are working on official documentation of how to configure nginx for use with the Sync Gateway. In the meantime, there have been several threads here very recently discussing it, that may be helpful. (You'll see a lot of references to a problem with WebSockets. We've figured this out; the workaround is to make sure to specify an explicit port number in the replication URL, even if it's the default SSL port 443; e.g. "https://example.com:443/db/ <https://example.com/db/>".) —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/42F4F39D-493B-4612-AC38-CEF22601EF09%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
