HTTP Post under the hood

POST reply behavior

While true, more often than not the server replies with a 200-ok status code and some extra information.

Whether this is by mistake or to avoid chatty apis or some other architecture/design consideration, only the developer can tell.

So in theory you get a 201 with an identifier and then make a GET request with said identifier to retrieve details.

In practice a lot of times this does not occur. So it is not safe to assume this behavior.

Your problem

I highly doubt that there is a built in mechanism that retries post. There are plenty of reasons for that:

1. Duplicating entries. Imagine creating a PayPal payment. If the network has an error and you just did not receive the answer, the built in mechanism will charge you twice.
2. There are libraries that do that only when you are sure that the request is idempotent, that is the post contained some sort of identifier and the second request will fail.