On Mon, Sep 27, 2010 at 6:55 PM, Thijs Koerselman <thijskoersel...@gmail.com> wrote: > The error appears to be something that magically happens after a > while. Restarting the server makes it go away again. The lualogging > mechanism is working again as well, so I managed to print some > debugging info.
I fixed that bug in the trunk several months ago, but I have no idea why I didn't release 1.3.5 with the bugfix... Norman Clarke has added some new features that are enough to make the next release 1.4, I will check with him if I can do that and get this bug fixed for anyone not using the trunk. It is so easy to run the trunk when using LuaRocks that I sometimes forget that bugs can go unfixed. :-) Sorry for the delay in answering, I was only accessing the internet through my phone in the last few days. > I now get an error because the POST data I am reading from wsapi_env > is empty. How do I get to the post data? I've tried this: > > function run(wsapi_env) > local myPostData = wsapi_env.POST > ... > > I'm quite sure my soap call is correct, so I'd expect the POST field > to contain something. Is this the right way to get to this data? If you want the raw postdata you have to call wsapi_env.input:read(). If you decode it with [[ req = wsapi.request.new(wsapi_env) ]] you get a request object that has the propertly parsed postdata in req.POST. > Thijs > -- Fabio Mascarenhas _______________________________________________ Kepler-Project mailing list Kepler-Project@lists.luaforge.net http://lists.luaforge.net/cgi-bin/mailman/listinfo/kepler-project http://www.keplerproject.org/
