[AX-715] After site rename, old name redirect only works on browser and not any other API

Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

After a site is renamed, the old URL should still work.
However, it only works as intended via the browser. API calls only show redirects.

Perform a site rename as described here
Try calling an issue using both the old and new site names via the browser.
Old: https://old-name.atlassian.net/rest/api/3/issue/<issuekey>
New: https://new-name.atlassian.net/rest/api/3/issue/<issuekey>
Result: Both give the result, the old-name link redirects to the new name.

Try calling the issue using the GET issue endpoint via Postman.
Old: https://old-name.atlassian.net/rest/api/2/issue/<issuekey>
New: https://new-name.atlassian.net/rest/api/2/issue/<issuekey>
Result: The new-name API call works, but the old-name API only shows 302 redirects.

API calls (ie via Postman or terminal) should also show the output the same as in the browser.

Old: https://old-name.atlassian.net/rest/api/2/issue/<issuekey>
New: https://new-name.atlassian.net/rest/api/2/issue/<issuekey>

This is the intended behavior. For API calls, please use the new site name for calling endpoints.

relates to

AX-623 After site rename, REST API calls failing with 401/403/404 response code

There are no comments yet on this issue.