Hello,
I use web2py (2.16.1) on 2 environments:
1. Embedded Rocket wsgi server
2. Deployed on nginx+uwsgi
I have the same application on both env, connected to the same database.
The application uses Basic Authentication, like in the example:
def f1():
auth.basic() if auth.user:
*## do something ...* else:
*## raise defined auth exception*
What is strange, the problem occures only on nginx+uwsgi:
1. If I call it without basic authorization it will raise defined exception
correctly
2. The problem is when I put header with correct authorization - it
raises *Internal
error Ticked issued: uncoverable*, and there is no any traces in logs.
The solution is putting *session.forget() *before *auth.basic()*, but why?
Could someone explain me the impact of session.forget() for that behaviour?
According documentation it is used to avoid storing session ( and it
is understandable)
Regards,
Tomasz
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/web2py/CAGTupug64paY%3Domb8n_o26F8RmZ9wyB8rt8n-hCpuvb1T2vu%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
