Hello,

This is a problem I have been seeing from the very beginning of interacting with Atmos (from v 0.5).

Frequently, we get a HTTP error "403 (Forbidden)" when we try to create/update an object; when we retry the same operation, changing nothing except recalculating the signature (since time of request has changed), we succeed. But a successful retry is not guaranteed; sometimes successive retries fail with the same 403 error; and we succeed on the 10th or 15th retry.

We never have to change the shared secret, the headers, time or the algorithm used: just retrying a number of times makes the request successful. This leaves the client application in a big dilemma on what to do.

My questions are:

1. Is this a known issue?
2. What is the cause of this problem?
3. How should a client app deal with this? We cannot keep retrying on a 403 without knowing if the "shared secret" provided by the user is wrong or if Atmos is responding incorrectly. Further, we don't know how many times to retry since the success of a retry is random.

This is a critical issue for us at this time as the reliability of the service we provide to the end-user is dependent on consistent behavior and accurate error reporting. Thank you for your help.

HTTP Error: 403

Atmos Error: 1032

Atmos Error String: There was a mismatch between the signature in the request and the signature as computed by the server.

Navneeth