9/19/2023 0 Comments Sitesucker retry 404 errors![]() ![]() ![]() The document size in the request exceeded the allowable document size for a request. Retry the request after reading the latest version of the resource and updating the eTag on the request. The operation specified an eTag that is different from the version available at the server, that is, an optimistic concurrency error. For partitioned collections, ID must be unique within all documents with the same partition key value. Use another ID for the resource to resolve this issue. The ID provided for a resource on a PUT or POST operation has been taken by an existing resource. This code is returned when a stored procedure, trigger, or UDF (within a query) does not complete execution within the maximum execution time. The operation did not complete within the allotted amount of time. For example, the resource may have already been deleted. The operation is attempting to act on a resource that no longer exists. Direct REST client must perform GET on DatabaseAccount to identify the current write region and forward the write request to that endpoint. This status code is used as a redirection code by drivers to forward the write requests to a new write region. 403.3 – This status code is returned for write requests during the manual failover operation. Any requests originating from machines outside the allowed list will receive a 403 response. 403 forbidden error is returned when the firewall rules configured on your Azure Cosmos DB account block your request. 403 can also be returned when a stored procedure, trigger, or UDF has been flagged for high resource usage and blocked from execution. An example of this scenario is when you try to add documents to a collection that has reached its provisioned storage. 403 code is also returned during a POST operation to create a resource when the resource quota has been reached. 400 is also returned when a request that requires an x-ms-documentdb-partitionkey does not include it.Ĥ01 is returned when the Authorization header is invalid for the requested resource. 400 is also returned when the consistent level for a GET operation is overridden by a stronger consistency from the one set for the account. In addition, a 400 can also be returned when the required properties of a resource are not present or set in the body of the POST or PUT on the resource. The JSON, SQL, or JavaScript in the request body is invalid. POST on a stored procedure resource to execute the stored procedure.Ī POST operation to create a resource is successful. One of the following REST operations were successful: - GET on a resource. New theory, I think to retry 400 response codes with retry-all-errors the following lines need tweaking (never played with C so apologies if I'm way off again).This article provides the HTTP status codes returned by the REST operations. Reading the code again I think this was way off. I think this is because -fail is causing this if to hit and the 400 to be counted as an error. I think either a note in the docs for retry-all-errors to highlight that -fail is needed to retry http error codes or tweaks to the source so any http error code is retried when retry-all-errors is set. This option is used together with -retry. I expected the 400 response to be retried. curl "" -retry 5 -retry-all-errors -X POST -fail will retry the 400 response. The endpoint returns a 400 status code with a body of hello world.Ĭurl doesn't retry the request and returns the body.Īfter reading through the code I discovered that by adding -fail to the command I could get the behaviour that I wanted. First up, thanks for curl it's awesome! I did thisĬurl "" -retry 5 -retry-all-errors -X POST -v ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |