On Fri, May 31, 2013 at 10:41 PM, Stephen Bartell <[email protected]> wrote: > Benoit, I mentioned that in my email. I'll repaste it here: > > By the way, I gave https_global_handlers a try. This seems to work fine if > the database is local. However, it doesn't work if the destination is remote > and authentication is involved. Is this because the remote database does not > have a session? Is it because auth isn't passed through the proxy? Is this a > bug? >
i misread that part sorry :) Did you try to pass the auth in the url ? ie. http://user:pass@.... if it doesn't work, adding that feature should be easy. - benoit > > On May 31, 2013, at 1:34 PM, Benoit Chesneau <[email protected]> wrote: > >> On Fri, May 31, 2013 at 9:53 PM, Stephen Bartell <[email protected]> wrote: >>> Thanks guys. >>> >>> Benoit, it looks like the alias improvement you are talking about is >>> couchdb-1736? It still looks like its baking. What I need is something a >>> little bigger than aliases though. I'd like the ability to redirect to a >>> remote Couch. >> >> You can probably use the proxy handler in couch to do that >> >> [httpd_global_handlers] >> remotedb = {couch_httpd_proxy, handle_proxy_req, >> <<"http:/host:port/remotedb">>} >> >> - benoit >
