On Fri, Nov 11, 2011 at 9:24 AM, Jan Lehnardt wrote:
> It'd break CouchApps that expect the redirect by default.
>
> For the sake of not breaking API's I'd suggest a config setting that
> enables Benoit's proposed behaviour that we can make the default for
> 2.0.
+1
On Nov 11, 2011, at 08:22 , Dave Cottlehuber wrote:
> On 30 October 2011 09:48, Benoit Chesneau wrote:
>> Hi all,
>>
>> I'm starting to hate our authentication system. We have now an
>> authentication system which default behaviour is to answer to browsers
>> or ajax calls. Ie we redirect on fa
On 30 October 2011 09:48, Benoit Chesneau wrote:
> Hi all,
>
> I'm starting to hate our authentication system. We have now an
> authentication system which default behaviour is to answer to browsers
> or ajax calls. Ie we redirect on fail login. Last change for example
> in cookie auth make the AP
On Sun, Oct 30, 2011 at 17:26, Jason Smith wrote:
> On Sun, Oct 30, 2011 at 5:43 PM, Johs Ensby wrote:
>> Thanks for raising this question, Benoit!
>>
>> Having worked with CouchDB as an all-in-one solution for deploying small web
>> sites and couchapps, the authentication system is the main sou
On Sun, Oct 30, 2011 at 5:43 PM, Johs Ensby wrote:
> Thanks for raising this question, Benoit!
>
> Having worked with CouchDB as an all-in-one solution for deploying small web
> sites and couchapps, the authentication system is the main sources of
> irritation. How on earth do I make this work?
Thanks for raising this question, Benoit!
Having worked with CouchDB as an all-in-one solution for deploying small web
sites and couchapps, the authentication system is the main sources of
irritation. How on earth do I make this work?
An example:
- push the app to a publicly available db so you
Hi all,
I'm starting to hate our authentication system. We have now an
authentication system which default behaviour is to answer to browsers
or ajax calls. Ie we redirect on fail login. Last change for example
in cookie auth make the API raises a 401 only when fail parameter is
given in the uri.