[jira] [Updated] (SLING-11279) Make SlingClient.exists() more resilient with http retries codes

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

     [ https://issues.apache.org/jira/browse/SLING-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thierry Ygé updated SLING-11279:
--------------------------------
    Description: 
Currently if we are in cluster with affinity cookie and use httpRetries code to retries on 404 to avoid sync problems, the exists() method can be confused for 404 responses. 
In order to fix it, it need to explicitely list generally expected code that might not need retries in that context.


  was:SlingHttpResponse.getSlingLocation and other get methods should work when the HTML response is customised by adding things like class="" in order to test the customised application.


> Make SlingClient.exists() more resilient with http retries  codes
> -----------------------------------------------------------------
>
>                 Key: SLING-11279
>                 URL: https://issues.apache.org/jira/browse/SLING-11279
>             Project: Sling
>          Issue Type: Improvement
>          Components: Apache Sling Testing Clients
>    Affects Versions: Apache Sling Testing Clients 3.0.12
>            Reporter: Thierry Ygé
>            Priority: Major
>
> Currently if we are in cluster with affinity cookie and use httpRetries code to retries on 404 to avoid sync problems, the exists() method can be confused for 404 responses. 
> In order to fix it, it need to explicitely list generally expected code that might not need retries in that context.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)