This is what I have concluded...
The problem is that many Windows based JSON-RPC serializers
(Including jayrock) and proxy's append a 3 byte UTF-8 BOM (Byte Order
Mark) to the beginning of the resulting encoded JSON text that is sent
in the body of the HTML request. Note that this is not a
If you go to the web2py server admin app e.g. http://127.0.0.1:8000/admin
and login you should see the name of the app containing the service and an
errors link after the name. Click that and you will see the errors page and
be able to see the stack trace.
When running as a Python process you
I wish I was at the point of resolving encoding issues. Right now
every time I call the service, the only thing I get in the response is
the web2py Ticket Issued html page returned as a string. Any
suggestions?
On May 22, 9:42 am, nick name i.like.privacy@gmail.com wrote:
I am doing
Can you post the error messages?
I am doing something similar, but using the .NET built in JSON DataContract
serializer. The things I've hit so far:
a) Anything other than a 200 return will raise an exception
(understandable), but not give you access to the returned json (bad; e.g.
403 responses often have useful data with
5 matches
Mail list logo
