Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of george.pucea@gmail.com
 designates 209.85.160.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=IFX89BGU5XAyWQp7pIylg5nlz66L8fzsYzK4CWGlRk8kpU1AifwILS3IGDT5sZ31J6
         8kBGDQXx/BVdi6kBEIs4C3XpHgc8LfY8RixcQCQvzKtc3a0Bil6qJKWwvObl7OmVDrYF
         Qa+3uVbEGNZaH+7OAYIaf/vWftBnI/hRp+gEQ=
MIME-Version: 1.0
In-Reply-To: 
 <08382548D50D3049BD5599E1E3146B34106E1A4C45@exgtmb06.nam.nsroot.net>
References: <AANLkTimbn5JG1erLRH7F0mLQPjS-KUMSgNnVHBvOJOi2@mail.gmail.com>
	<08382548D50D3049BD5599E1E3146B34106E1A4C45@exgtmb06.nam.nsroot.net>
Date: Thu, 3 Jun 2010 19:47:17 +0300
Message-ID: <AANLkTikeptrgTMwC9GDQcEl8AGN4O7xKv8P6S182npd_@mail.gmail.com>
Subject: Re: HTTP Status 400 - Invalid direct reference to form login page!
From: Gheorghe Pucea <george.pucea@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=0016e68ee21d97722f048822f5f8

--0016e68ee21d97722f048822f5f8
Content-Type: text/plain; charset=ISO-8859-1

Hello Barry,


  Thank you very much for your quick respone, but I think that version of
Tomcat was very old compared to Tomcat 6.0.26 I think the problem should be
fix by now.
  So you suggest that I manually should clear my browser's cache?And this
should fix my problem?


On Thu, Jun 3, 2010 at 7:10 PM, Propes, Barry L <barry.l.propes@citi.com>wrote:

> I had that happen periodically for years with my version of TC 4.1.31.
>
> With some folks, we could get it to go away, by cleaning out browser cache.
> With others, it was the same people that incurred it all the time. They
> could access "other" protected areas, but not the one.
> I ended up making a duplicate non-protected piece for them. For me it
> wasn't a big deal, because they already were -- in a sense -- in a protected
> piece to begin with. But it would have been better if it'd worked.
>
> -----Original Message-----
> From: Gheorghe Pucea [mailto:george.pucea@gmail.com]
> Sent: Thursday, June 03, 2010 9:30 AM
> To: users@tomcat.apache.org
> Subject: HTTP Status 400 - Invalid direct reference to form login page!
>
> Hello,
>
>
>
>  I have a problem with my Tomcat instance, I'm using:
>
>
> Tomcat 6.0.26
> Java jdk 1.5.0_17
> Windows XP SP3
>
>
>   I have implemented a JAAS login module for my application and everything
> goes fine except from one thing.
>
> Here are the steps that I am doing:
>
>
> 1)Request a protected resource  -> the login form show's up and I enter my
> username and password
> 2) I get into the application and everything looks fine but when I get back
> to the login page and enter my username/password again I get the message:
> (If I refresh the login page immediately when I hit the logout button
> everything goes weel) HTTP Status 400 - Invalid direct reference to form
> login page
> ------------------------------
>
> *type* Status report
>
> *message* *Invalid direct reference to form login page*
>
> *description* *The request sent by the client was syntactically incorrect
> (Invalid direct reference to form login page)*
>
> *
> *
>
> *
> *
>
> *
> *
>
> *Thank you very much!*
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--0016e68ee21d97722f048822f5f8--