I am also experiencing this issue. I see this in routes.example.py:
--snip--
# In the event that the error-handling page itself returns an error, web2py will
# fall back to its old static responses. You can customize them here.
# ErrorMessageTicket takes a string format dictionary containing
A couple of questions have come up about routes_onerror in routes.py.
Refreshing our memory, here's a fragment of routes.example.py:
# Error-handling redirects all HTTP errors (status codes = 400) to a specified
# path. If you wish to use error-handling redirects, uncomment the tuple
# below.
On Feb 17, 2011, at 7:53 AM, David J. wrote:
I did notice one 'race' condition;
If you have an app that has an error in models/db.py
and you have */400 in routes.py your going to continuously be redirecting
your self to the same page until the browsers own error handling kicks in and
3 matches
Mail list logo
