I suppose that's possible. On Sunday, November 23, 2014 6:53:42 PM UTC-5, Jens Alfke wrote: > > Yikes! Since the problem went away after a meaningless change to the URL, > maybe it had something to do with caching? Maybe WebKit had cached a bad > response from the first URL, so when you changed to the second equivalent > URL it sent the request again and got a better response? > > —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/be3df6e0-04a7-44e3-9909-2fed95f5790d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
