Change Details

We compute the next target index from the api. But did not re-urlencode it. The bitbucket lister answered to this inconsistently... Thus creating next link identical to the current one... Thus making the lister refuse to continue further). This fixes that behavior re-urlencoding correctly the index. Related T1826 Depends D1633

We compute the next target index from the api. But did not re-urlencode it. The bitbucket lister answered to this inconsistently... Thus creating next link identical to the current one... Thus making the lister refuse to continue further). This fixes that behavior re-urlencoding correctly the index. Related T1826 Depends on D1633

We compute the next target index from the api. But did not re-urlencode it. The bitbucket lister answered to this inconsistently... Thus creating next link identical to the current one... Thus making the lister refuse to continue further). This fixes that behavior re-urlencoding correctly the index. Related T1826 Depends on D1633