Hello. There might be a potential problem with how Fiddler handles requests sent by CouchBaseClient constructor. Basically the observed behavior is that ctor hangs. See this SO discussion: http://stackoverflow.com/questions/21390152/couchbase-net-client-getting-stuck-in-the-constructor
1 Answer, 1 is accepted
0
Hi, Dmitry--
If you have a self-contained repro project for this, I'd be happy to take a look.
Have you enabled Streaming (click the button in Fiddler's toolbar)? If not, a poorly-written client framework could deadlock.
Other than that, the most likely issue with CouchBase having problems with proxies is that the client is failing to properly clean up resources and thus hits a connection pool (or similar) limit and blocks waiting for a connection that never becomes free. There's nothing that Fiddler or another proxy could do to fix this.
Regards,
Eric Lawrence
Telerik
If you have a self-contained repro project for this, I'd be happy to take a look.
Have you enabled Streaming (click the button in Fiddler's toolbar)? If not, a poorly-written client framework could deadlock.
Other than that, the most likely issue with CouchBase having problems with proxies is that the client is failing to properly clean up resources and thus hits a connection pool (or similar) limit and blocks waiting for a connection that never becomes free. There's nothing that Fiddler or another proxy could do to fix this.
Regards,
Eric Lawrence
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.