[Authentication] Handle 401 responses safely by clearing auth token and navigating without forced page reload

[mohdsubhan1756]

axiosInstance redirects users to / on every 401 Unauthorized response using window.location.href. The stored auth token is not cleared before redirecting, which can leave invalid credentials in localStorage and repeatedly trigger unauthorized requests after reload.

Using window.location.href also forces a full page reload instead of SPA navigation, causing poor UX and possible redirect loops.

[mohdsubhan1756]

Hi,
I would like to work on this issue under GSSOC 2026,
Kindly assign this to me.

[shhivamverma]

Hello,

I would like to work on this issue under SSoC 2026.

I reviewed the issue and understand that the current 401 handling leaves stale authentication tokens in localStorage and performs a full page reload using window.location.href. I would be happy to work on improving the authentication flow by safely clearing invalid tokens and implementing proper navigation to provide a better user experience.

Could you please consider assigning this issue to me if it is still available?

Thank you.

[anshhika-shukla]

Hi,

I am interested in working on this issue under SSoC 2026.

After reviewing the issue details, I understand that the current 401 Unauthorized handling can leave invalid authentication data stored on the client side and may cause unnecessary page reloads. I would like to contribute by improving the authentication flow and ensuring smoother navigation and session handling.

If this issue is still available, kindly consider assigning it to me.

Thank you.