[jira] [Created] (SLING-11125) SlingClient.exists(...) should use expected status in order to support http retries parameters

["Thierry Ygé (Jira)" <ji...@apache.org>]

Thierry Ygé created SLING-11125:
-----------------------------------

             Summary: SlingClient.exists(...) should use expected status in order to support http retries parameters
                 Key: SLING-11125
                 URL: https://issues.apache.org/jira/browse/SLING-11125
             Project: Sling
          Issue Type: Bug
          Components: Apache Sling Testing Clients
    Affects Versions: Apache Sling Testing Clients 3.0.8
            Reporter: Thierry Ygé


Currently if tests need to retries on some errors which are likely to happen in clustered setup (AEM in Cloud for example).

usually the use of "-Dsling.it.http.retriesErrorCodes=401,404,405,429,500,501,503" would include 404 cases.

The issue is then SlingClient.exists(...) would always fail in case we try to check for "not existing path" as the test would expect also 404 to be returned.

The current implementation of ServerErrorRetryStrategy support that if the expected values are passed , this would bypass the retriesErrorCodes.

Thus it would make sense to pass the possible returned code for the request done by SlingClient.exists(...) call.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)