if the request comes in either as a POST or as a PUT it has a body (since all examples report a faily nested query structure, I'd say it's the case vs a simple querystring in a GET)
If the body carries the correct content-encoding, it's automatically parsed into request.vars. You can still read the raw body as usual in request.body . On Tuesday, November 15, 2016 at 10:50:23 PM UTC+1, Dave S wrote: > > I'm trying to implement a simple json endpoint for Grafana. Does anyone > here have experience with doing this? > > <URL: > https://github.com/grafana/simple-json-datasource/blob/master/README.md> > > I'm looking at using @service.json, but I'm not sure how to get the body > on a /query. > > (The sample fake-simple-json-datasource is a server written in > javascript! It doesn't make clear if the /query is a POST or a GET, and if > it's a GET how the body gets done.) > > /dps > > -- 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.
