ketting | The HATEOAS client for javascript | REST library

There's two main reasons/processes to do POST requests with Ketting.

1. To create a new resource / add a new resource to a collection.
2. To do an arbitrary RPC call / submit a form.

When you use the useResource() hook, and use the submit() function, the primary purpose of this is to deal with the first case.

Because you are strictly making a new resource, the expectation is that the response contains:

1. A 201 Created status
2. A Location header pointing to the newly created resource.

Optionally, you the server can return the body of the newly created resource, but to do that, the server must also include a Content-Location header.

If that was your purpose, you can get the result of the POST request simply by listening to state changes in the component you already have.

If you are in the second category and just want to do an arbitrary POST request and read the response, you should not use the submit() function returned from the hook.

The submit() function on the useResource hook is really used as a 'resource state submissions' mechanism, and it's not good to overload this for other arbitrary POST requests.

Instead, just use the .post() function on the Resource itself.

Amazing! Thank Thorsten Rintelen so much! Your info solved my problem that lasted for about two weeks. I was enabled http/2 for the apache webserver ( according to the guide on the web: https://www.howtoforge.com/how-to-enable-http-2-in-apache/ after enabling https in server-side)

====> This article is solved!