What I said was that if you print on the server-side you can see what happens on the "endpoint" you have control of: not IOS, the webserver!
On Tuesday, October 23, 2012 3:27:46 PM UTC+2, Mchurch wrote: > > from the app, no more errors, always that "500". > >> try to print out request.vars and request.vars.body.read() and see their >> contents. >> > > I have to think and study more about that; it's a json call, i can't > reach directly that page, i should give the server response back to the app > to check what web2py reads. > But from IOS i don't know (yet) how to do! > Thanks Niphlod. > > Il giorno martedì 23 ottobre 2012 11:55:16 UTC+2, Niphlod ha scritto: >> >> that's the problem when you don't know what something does..... >> >> try to print out request.vars and request.vars.body.read() and see their >>> contents. >> >> >> PS: you can also watch the errors for the app to investigate the issue >> (if your phone is getting a 500, it's probable that the error is logged in >> web2py) >> >> --
