Implement backward compatibility for legacy challenge urls(v4) - Sometimes redirection does not work

[SathyaJayabal]

#4435 (comment)

example:https://test-community-app.topcoder-dev.com/challenges/30056660

[srjr19]

@SathyaJayabal @sushilshinde as per last comment, this seems now fixed - just tested on test env several times and it redirects fine https://test-community-app.topcoder-dev.com/challenges/30056660 .

[SathyaJayabal]

@sushilshinde , please hold off on opening this for pickup until we can verify if this is already fixed in the latest deployment.

cc: @simranb86

[lakshmiathreya]

Seems intermittent -

[SathyaJayabal]

@sushilshinde @simranb86 , we still face the issue.

[srjr19]

@SathyaJayabal @sushilshinde here is root cause of the problem. So once we fix #4505 , this intermedittent will be fixed. If you want I can try to push a fix for #4505 today ? Feel free to assign that to me if other developer cannot fix it and then let's see how it fix goes about it.

Else the backward compatibility redirect is working great.

[sushilshinde]

@simranb86 do we need review types for no-auth calls?

[srjr19]

@simranb86 do we need review types for no-auth calls?

@sushilshinde no review types is auth based call. I guess that is reason why we say animation forever in other ticket also - I have pushed one PR to make sure we check for auth before making call to challenge-api. That change should also fix #4505

If you are checking like should we make that reviewTypes call as no auth on challenge-api side, then yes, we can as it has no security data or risk.

Let's revisit once that PR is merged.

[SathyaJayabal]

@sushilshinde, issue is not observed now.
cc @lakshmiathreya