Closed mataanin closed 12 years ago
now it returns. Still working bad: "{\"sessionID\":\"TxpYK0SshMG20fj6fJ05CNnA\"}"
Don't know where is the bad thing? it returns the sessionID, and you could get it now
This is not valid JSON. Java standard parser classes can't parse it.
On Thu, Nov 17, 2011 at 10:00 PM, Xiaohang < reply@reply.github.com
wrote:
Don't know where is the bad thing? it returns the sessionID, and you could get it now
Reply to this email directly or view it on GitHub: https://github.com/sizzlelab/side/issues/45#issuecomment-2781059
Any update on this one?
When should we expect it fixed?
On Thu, Nov 17, 2011 at 10:07 PM, Maksim Golivkin maksim@golivkin.euwrote:
This is not valid JSON. Java standard parser classes can't parse it.
On Thu, Nov 17, 2011 at 10:00 PM, Xiaohang < reply@reply.github.com
wrote:
Don't know where is the bad thing? it returns the sessionID, and you could get it now
Reply to this email directly or view it on GitHub: https://github.com/sizzlelab/side/issues/45#issuecomment-2781059
Done
Fixed.
Does new api implement new error code functionality?
Postponing due to low priority.
a simple html file with following code, doesn't work: