Primarily because I would like to display custom messages sent from the API, and I want them controllable from the API side. Specifically, our UI framework has a feature built in which allows us to display custom messages from the API by specifying the message characteristics in the response body. These characteristics need to be in JSON.
We can specify the messages on other authenticated requests and have them display fine, but we'd prefer to not have to make a custom case for handling this non-JSON unauthenticated request. On Thursday, September 4, 2014 10:38:06 AM UTC-7, Leonel Câmara wrote: > > Why? Why don't you simply analyse the HTTP return code where you're > calling the API? > -- 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. For more options, visit https://groups.google.com/d/optout.
