Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B28710C62 for ; Sun, 1 Dec 2013 21:06:03 +0000 (UTC) Received: (qmail 14054 invoked by uid 500); 1 Dec 2013 21:05:59 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 13927 invoked by uid 500); 1 Dec 2013 21:05:59 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 13918 invoked by uid 99); 1 Dec 2013 21:05:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Dec 2013 21:05:59 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Dec 2013 21:05:52 +0000 Received: from [192.168.245.216] (montserrat.wissensbank.com [212.85.37.175]) (Authenticated sender: andre.warnier@ice-sa.com) by tor.combios.es (Postfix) with ESMTPA id 78A093C0068 for ; Sun, 1 Dec 2013 22:05:56 +0100 (CET) Message-ID: <529BA499.4000101@ice-sa.com> Date: Sun, 01 Dec 2013 22:05:29 +0100 From: =?windows-1252?Q?Andr=E9_Warnier?= Reply-To: Tomcat Users List User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: j_security_check error References: <000b01ceeebd$65d635d0$3182a170$@me.com> In-Reply-To: <000b01ceeebd$65d635d0$3182a170$@me.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org J. Brian Hall wrote: > I�m using Tomcat and a MySQL database that contains > usernames/passwords/roles for form-based authentication. Logging in with > correct username/password successfully directs to index.jsp (from > login.jsp). Logging in with incorrect username/password successfully > directs to error.jsp (from login.jsp). However, an unsuccessful login > followed by attempting to login with the correct username/password leads to > an HTTP Status 404 j_security_check error that says the requested resource > is not available. Does anyone know what may be wrong? Here are the details > of my configuration. > To understand what is going on there, I suggest that you install a browser plugin such as HttpFox, Live HTTP headers, or Fiddler2(for IE), and that you have a look at which request URLs and HTTP headers are really being sent by the browser to the server (and vice-versa), at each step. Probably what happens is that the original URL requested by the browser is lost somewhere when you go through the error page, and that by the time you do the second (correct) authentication, the server does not know anymore where to forward the (now authenticated) request to. So it ends up being forwarded to some invalid URL, and you get back a 404 error. What does your "error.jsp" page really look like ? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org