[Security] CORS failures not distinguished from generic network errors in axios interceptors

[RUKAYAT-CODER]

Overview

axios.config.ts treats CORS failures and generic network errors identically. CORS rejections often indicate a misconfigured backend or a man-in-the-middle scenario and should be flagged separately in monitoring.

Specifications

Features:

• Detect CORS errors by checking error.message for "Network Error" with a 0 status code on non-GET requests
• Log CORS failures to Sentry with a distinct cors_failure tag

Tasks:

• Add CORS detection logic in the response error interceptor
• Create a distinct Sentry issue category for CORS errors
• Write a test that mocks a CORS response and checks the Sentry tag

Impacted Files:

• src/config/axios.config.ts

Acceptance Criteria

• CORS failures appear in Sentry under a unique cors_failure tag
• Generic network errors continue to use existing error handling
• Test confirms correct categorisation

[muhahahmad68]

@muhahahmad68 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Kindly assign to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @muhahahmad68 to this issue.

[collinsezedike]

@collinsezedike has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I'd like to take on this issue! Distinguishing CORS rejections from generic network drops gives us much better observability into backend misconfigurations or potential proxy issues in Sentry.

Implementation Plan

1. Implement CORS Failure Detection (src/config/axios.config.ts):

   • In the Axios response error interceptor, add a helper to detect CORS failures:
     • Check if error.message === 'Network Error'
     • Check if !error.response or error.response.status === 0
     • Confirm request method was non-GET (error.config?.method?.toLowerCase() !== 'get')

2. Tag & Report to Sentry:

   • When a CORS failure is detected, capture the exception/event in Sentry with a distinct tag (tags: { category: 'cors_failure' }) or custom fingerprint so Sentry categorizes it separately from routine offline errors.
   • Fall back to standard network error handling for genuine offline/timeout events.

3. Unit Tests:

   • Mock a failed Axios request simulating a CORS rejection (message "Network Error", no response / status 0, POST method) and verify Sentry gets called with { category: 'cors_failure' }.
   • Mock a standard GET network error and confirm it continues using the default network error handler.

Ready to start as soon as assigned!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @collinsezedike to this issue.

[akansmafengadamu]

@akansmafengadamu has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer, Please assign this issue to me so I can resolve it, Thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @akansmafengadamu to this issue.

[drips-wave]

Congratulations, @akansmafengadamu! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @akansmafengadamu: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊