> On Dec 12, 2014, at 6:24 AM, Vinay Bhinde <[email protected]> wrote: > > The only major issue right now is that i cannot figure out why does my ios > client fail to authenticate with SG inspite of session cookie being valid and > not expired.
Looking back through this thread, I think it's the bug I mentioned about the "Cookie" header being ignored when you set it as a custom header in the _replicate call. But it's hard to tell with all the back-and-forth. Have you filed an issue <https://github.com/couchbase/couchbase-lite-ios/issues>? I can't find one. That's a better way to track this than email discussion. > Any help for where should i check and what's going wrong (any specific logs > so that i can search to find if cblite requests take my cookie along when > they call SG) because for the first time client successfully authenticates. See if you can sniff the HTTP traffic between app and server. Then you can see what Set-Cookie headers the server sends and what Cookie headers the app sends. A proxy like nginx in front of the Sync Gateway should be able to do this, or you can run a debugging proxy like Charles <http://www.charlesproxy.com/> on your client network and configure your device (or simulator) to connect through it. —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/5B7BFCD4-6887-4648-9EF7-4FB7ADA79976%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
