If you leave quotes off of the property names, it's not json and the
request cannot be parsed at all. Why that shows up as a response allocation
error, i can't say off hand. It's a bug - the response should be that the
request is missing data/parameters.
----- stephan
Sent from a mobile device, possibly from bed. Please excuse brevity, typos,
and top-posting.
On Jun 6, 2017 23:04, "Warren Young" <war...@etr-usa.com> wrote:
On Jun 6, 2017, at 1:09 PM, Offray Vladimir Luna Cárdenas <off...@riseup.net>
wrote:
>
> I don't know how the page name is supposed to be given in the URL.
The document you point to says it’s supposed to be sent in the payload, not
in the request URL:
$ curl -H "Content-Type: application/json" \
-d '{"authToken": "nunyabinness", \
"payload": {"name": “foo", "content": "bar"} }' \
http://localhost:8080/json/wiki/create
Incidentally, I found a bug while working that incantation out: if you
leave off the quotes around the property names, you get
fossil: Fatal error: could not allocate response object
on the console that is running the Fossil server instance. All errors that
occur down the /json path should give a JSON reply, not kill off the forked
child with a vague and highly nonhelpful error.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
