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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Bug
• Affects Version/s: Apache Sling Testing Clients 3.0.10
• Component/s: Apache Sling Testing Clients
• Assignee: Unassigned
• Reporter: Thierry Ygé
• Created: 05/Feb/22 15:46
• Updated: 15/Jan/24 09:02
• Resolved: 15/Jan/24 09:02

Description

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.