Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BE629111F2 for ; Mon, 14 Apr 2014 07:58:13 +0000 (UTC) Received: (qmail 39247 invoked by uid 500); 14 Apr 2014 07:58:12 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 38922 invoked by uid 500); 14 Apr 2014 07:58:11 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 38914 invoked by uid 99); 14 Apr 2014 07:58:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2014 07:58:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Apr 2014 07:58:06 +0000 Received: by mail-ve0-f177.google.com with SMTP id sa20so6932970veb.22 for ; Mon, 14 Apr 2014 00:57:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=FpbRWFNv7oTJBfCJfHoX7/+UTYAoF0GcUPtgh6dQrwE=; b=Vbz9ugqVieUgZ7mrS0Uh/za2GbFHLAGphTHEGIpz1Nv1QWyNktWr/A3hnPHRu/cJDP dGXJcOVfcpQF3qNNOTJv0Cs0GYo871LOCstlNWVGkKkM8IspXujaBXbbeaxcgYr+OAVF y3Nt7YI+eYZhceA1j31/a4PcpjzuKgQcqDX3HCxc+0Bn6x+FElYITofH/l4HjATboPd/ FpjmgAto2atnx2fwmCaKpW+yb3wqFc7q7r2GU837vNhVpDDWz8/nUK3KXDmBGWvLjw64 tQ7kxAe+N+ieZOaJ43iLpn7R7IOscd6zLtWg0SRpwAhQA9elY+uQ46/I9MNn5vG2v67Z cG0g== X-Gm-Message-State: ALoCoQlKLURpMxB3uml6jERmt/FGpVDq5ZJy8Bf6UpHtAMnqBu2/EP39OZhOEGjCyL7lh4c91le0 MIME-Version: 1.0 X-Received: by 10.52.23.97 with SMTP id l1mr29490379vdf.11.1397462263434; Mon, 14 Apr 2014 00:57:43 -0700 (PDT) Received: by 10.220.29.199 with HTTP; Mon, 14 Apr 2014 00:57:43 -0700 (PDT) Received: by 10.220.29.199 with HTTP; Mon, 14 Apr 2014 00:57:43 -0700 (PDT) In-Reply-To: <1397424531.24083.YahooMailNeo@web181703.mail.ne1.yahoo.com> References: <1397424531.24083.YahooMailNeo@web181703.mail.ne1.yahoo.com> Date: Mon, 14 Apr 2014 09:57:43 +0200 Message-ID: Subject: Re: authentication_redirect is not working. From: =?UTF-8?Q?Johannes_J=C3=B6rg_Schmidt?= To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=20cf3079bc64cca0bf04f6fc095d X-Virus-Checked: Checked by ClamAV on apache.org --20cf3079bc64cca0bf04f6fc095d Content-Type: text/plain; charset=UTF-8 Basically its because CouchDB assumes browsers are requesting JSON. https://issues.apache.org/jira/browse/COUCHDB-1175 is not resolved, because the devs were not able to gain consense. Greetings Am 13.04.2014 23:29 schrieb "Scott Weber" : > Lets start with this, because it is almost exactly what I am fighting > with, but it doesn't work for me, like it did appear to work for the person > how posted this: > > > http://stackoverflow.com/questions/18966385/couchdb-access-denied-redirect > > The application I am building is open to the public, using CouchDB for > it's authentication, and 100% inside CouchDB with all JS, CSS, HTML as > attachments. > > Logically the uses starts at a login page which has no security, and after > success login, are redirected to other databases that service page requests > (which are based on their name, role, etc...) > > When I go directly to a database without logging in, I can't access it. > Which is fine, except I am getting that rather dry message: > > > {"error":"unauthorized","reason":"You are not authorized to access this > db."} > Which is really counter intuitive for an application. > > I have set the authentication redirect as describe in the link, to send > them to the login page, but nothing happens. I still get the above dry > message. > > This is on both IE and FF. > > Any idea how to get an acceptable page? > > > -Scott --20cf3079bc64cca0bf04f6fc095d--