Well, i found something interesting.

My production server is running 3 CherryPy behind an Nginx http-
server. If I connect to each one of them directly, from within the
server, was_login_attempted() works fine. But if they get called from
my nginx server, it always returns True.

Anyone who is running TG behind Nginx can shade some light here? maybe
I'm misconfiguring Nginx in some way?

Thanks.

On Dec 16, 3:53 pm, "Yo'av Moshe" <[email protected]> wrote:
> Also,
> I now created a simple method:
>     @expose("json")
>     def wla(self):
>         return dict(msg=identity.was_login_attempted())
>
> and it shows:
> {"tg_flash": null, "msg": true}
>
> What could be wrong?
>
> Yo'av.
>
> On Dec 16, 3:44 pm, "Yo'av Moshe" <[email protected]> wrote:
>
> > Hey everyone,
> > I'm noticed an odd bug in my production environment - my login page
> > always show "The username or password you entered are incorrect", and
> > after checking that, I noticed that no matter what, the login method
> > always reads True for identity.was_login_attempted(). No matter what
> > 'msg=' I pass, it is always overwritten by the above text because
> > identity.was_login_attempted() returns True.
>
> > If it try it from tg-admin shell it works fine, and returns False.
>
> > My production machine is running TG1.0.7.
>
> > How does TG decides if login was attempted? I removed all the cookies
> > but it doesn't seem to be related.
>
> > Thanks.
> > Yo'av
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to