Re: HTTP Status 408!

2010-06-22 Thread neo21 zerro
@tomcat.apache.org Sent: Mon, June 21, 2010 7:52:40 PM Subject: Re: HTTP Status 408! On 21/06/2010 17:36, neo21 zerro wrote: Ok. Something like this ? URL protectedResource = new URL(http://localhost:8080/resource;); *URLConnection yc = *protectedResource*.openConnection

Re: HTTP Status 408!

2010-06-22 Thread Pid
you might only need to do this is a temporary measure. p *From:* Pid p...@pidster.com *To:* Tomcat Users List users@tomcat.apache.org *Sent:* Mon, June 21, 2010 7:52:40 PM *Subject:* Re: HTTP Status 408! On 21/06

Re: HTTP Status 408!

2010-06-22 Thread neo21 zerro
3.0, so you might only need to do this is a temporary measure. p *From:* Pid p...@pidster.com *To:* Tomcat Users List users@tomcat.apache.org *Sent:* Mon, June 21, 2010 7:52:40 PM *Subject:* Re: HTTP Status 408! On 21

Re: HTTP Status 408!

2010-06-21 Thread neo21 zerro
login from another aplication programmicaly to my app that runs on Tomcat with custom JAAS login module? From: Martin Gainty mgai...@hotmail.com To: Tomcat Users List users@tomcat.apache.org Sent: Fri, June 11, 2010 11:16:09 PM Subject: RE: HTTP Status 408! can you

Re: HTTP Status 408!

2010-06-21 Thread Pid
: Martin Gainty mgai...@hotmail.com To: Tomcat Users List users@tomcat.apache.org Sent: Fri, June 11, 2010 11:16:09 PM Subject: RE: HTTP Status 408! can you post all of the code (including the html that houses the flex components), display the full stacktrace and display environmental

Re: HTTP Status 408!

2010-06-21 Thread neo21 zerro
somehow to tell the FormAuthenticator what the saved request should be. Any ideas? Thanks!!! From: Pid p...@pidster.com To: Tomcat Users List users@tomcat.apache.org Sent: Mon, June 21, 2010 5:30:00 PM Subject: Re: HTTP Status 408! On 21/06/2010 15:20, neo21

Re: HTTP Status 408!

2010-06-21 Thread Pid
!!! *From:* Pid p...@pidster.com *To:* Tomcat Users List users@tomcat.apache.org *Sent:* Mon, June 21, 2010 5:30:00 PM *Subject:* Re: HTTP Status 408! On 21/06/2010 15:20, neo21 zerro wrote: Hello, Problem finally solved :) Pid was right my encoding was not ok and a Cookie was not passed over

Re: HTTP Status 408!

2010-06-21 Thread neo21 zerro
...@pidster.com To: Tomcat Users List users@tomcat.apache.org Sent: Mon, June 21, 2010 6:19:44 PM Subject: Re: HTTP Status 408! On 21/06/2010 15:48, neo21 zerro wrote: Ok.I already have send params from my other application to my Tomcat application and everything goes well, I make

Re: HTTP Status 408!

2010-06-21 Thread Pid
List users@tomcat.apache.org *Sent:* Mon, June 21, 2010 6:19:44 PM *Subject:* Re: HTTP Status 408! On 21/06/2010 15:48, neo21 zerro wrote: Ok.I already have send params from my other application to my Tomcat application and everything goes well, I make this with the j_security_check

Re: HTTP Status 408!

2010-06-11 Thread neo21 zerro
To: Tomcat Users List users@tomcat.apache.org Sent: Thu, June 10, 2010 10:35:48 PM Subject: Re: HTTP Status 408! On 10/06/2010 15:39, neo21 zerro wrote: Yes I am requesting a protected resource but I don't know why is this happening. I've tried to set all sort of cookies in my browser

RE: HTTP Status 408!

2010-06-11 Thread Martin Gainty
: neo21_ze...@yahoo.com Subject: Re: HTTP Status 408! To: users@tomcat.apache.org I installed the Tomcat 7 RC but the problem persists. So it's definitely a bug from my app. After the logout is made the redirect is made from flex(navigateToUrl - function) do you think this could be an issue

Re: HTTP Status 408!

2010-06-10 Thread Pid
On 09/06/2010 21:52, neo21 zerro wrote: Hello, I'm using Tomcat 6.0.26 with java 1.5 JDK. I've developed a JAAS login module for my application and when I try to login in my app a strange error occur's: HTTP Status 408:The time allowed for the login process has been exceeded.

Re: HTTP Status 408!

2010-06-10 Thread neo21 zerro
, June 10, 2010 12:13:34 PM Subject: Re: HTTP Status 408! On 09/06/2010 21:52, neo21 zerro wrote: Hello, I'm using Tomcat 6.0.26 with java 1.5 JDK. I've developed a JAAS login module for my application and when I try to login in my app a strange error occur's: HTTP Status 408

Re: HTTP Status 408!

2010-06-10 Thread neo21 zerro
List users@tomcat.apache.org Sent: Thu, June 10, 2010 12:13:34 PM Subject: Re: HTTP Status 408! On 09/06/2010 21:52, neo21 zerro wrote: Hello, I'm using Tomcat 6.0.26 with java 1.5 JDK. I've developed a JAAS login module for my application and when I try to login in my app

Re: HTTP Status 408!

2010-06-10 Thread Pid
Keep-Alive 115 Connection keep-alive Cookie JSESSIONID=3AFB0FC0977ABA49563E858035F02617 From: Pid p...@pidster.com To: Tomcat Users List users@tomcat.apache.org Sent: Thu, June 10, 2010 12:13:34 PM Subject: Re: HTTP Status 408! On 09/06/2010

Re: HTTP Status 408!

2010-06-10 Thread neo21 zerro
From: Pid p...@pidster.com To: Tomcat Users List users@tomcat.apache.org Sent: Thu, June 10, 2010 3:43:18 PM Subject: Re: HTTP Status 408! On 10/06/2010 12:06, neo21 zerro wrote: Hello , Good news I found a way to get rid of the error with this code in my JASS

Re: HTTP Status 408!

2010-06-10 Thread Pid
*From:* Pid p...@pidster.com *To:* Tomcat Users List users@tomcat.apache.org *Sent:* Thu, June 10, 2010 3:43:18 PM *Subject:* Re: HTTP Status 408! On 10/06/2010 12:06, neo21 zerro wrote: Hello , Good news I found a way

RE: HTTP Status 408!

2010-06-10 Thread Martin Gainty
que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Thu, 10 Jun 2010 06:19:36 -0700 From: neo21_ze...@yahoo.com Subject: Re: HTTP Status 408! To: users@tomcat.apache.org; p...@pidster.com Yes

Re: HTTP Status 408!

2010-06-10 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Neo21, On 6/9/2010 4:52 PM, neo21 zerro wrote: I'm using Tomcat 6.0.26 with java 1.5 JDK. I've developed a JAAS login module for my application and when I try to login in my app a strange error occur's: HTTP Status 408:The time allowed for the

Re: HTTP Status 408!

2010-06-10 Thread neo21 zerro
: Martin Gainty mgai...@hotmail.com To: Tomcat Users List users@tomcat.apache.org Sent: Thu, June 10, 2010 4:34:11 PM Subject: RE: HTTP Status 408! the form-login-page login.html *should* contain the j_security parameters for your login form e.g.: form method=POST action=j_security_check input

Re: HTTP Status 408!

2010-06-10 Thread neo21 zerro
versions of Tomcat ? I mean newer versions, like 7 ? Thanks for your time! From: Christopher Schultz ch...@christopherschultz.net To: Tomcat Users List users@tomcat.apache.org Sent: Thu, June 10, 2010 4:46:16 PM Subject: Re: HTTP Status 408! -BEGIN PGP

Re: HTTP Status 408!

2010-06-10 Thread Mark Thomas
On 10/06/2010 15:39, neo21 zerro wrote: Yes I am requesting a protected resource but I don't know why is this happening. I've tried to set all sort of cookies in my browser but nothing works.The problem is that I'm not using jsp like Pid said and I think I should try to use

Re: HTTP Status 408!

2010-06-10 Thread Konstantin Kolinko
2010/6/10 neo21 zerro neo21_ze...@yahoo.com:     Are there other versions of Tomcat ? I mean newer versions, like 7 ? There is RC 4 build of Tomcat 7 available for testing. See a thread on d...@. Best regards, Konstantin Kolinko

Re: HTTP Status 408

2006-11-01 Thread Christopher Schultz
Søren, I get a login error when the username or password is wrong but when it is correct I get the following error HTTP Status 408 - The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or

Re: HTTP Status 408

2006-02-01 Thread Tim Funk
The code says (in FormAuthenticator) if (session == null) session = request.getSessionInternal(false); if (session == null) { if (containerLog.isDebugEnabled()) containerLog.debug (User took so long to log on the session

Re: HTTP Status 408

2006-02-01 Thread scott soward
Thank you Tim, I'll try your suggestions. Scott --- Tim Funk [EMAIL PROTECTED] wrote: The code says (in FormAuthenticator) if (session == null) session = request.getSessionInternal(false); if (session == null) { if (containerLog.isDebugEnabled())