CORS Configuration Update for Deployment

[rishyym0927]

To address the CORS issue for your project, I recommend creating an issue that outlines the current limitation and the desired solution. Here’s an example of how to word the issue:

---

Description:

The current CORS configuration allows requests only from http://localhost:5173. However, this needs to be updated to support requests from the deployed environment as well, allowing access to the API when hosted publicly.

Current Behavior:

• Only requests from http://localhost:5173 are accepted.
• This limits the accessibility of the API once the project is deployed.

Expected Behavior:

• The CORS policy should allow requests from:
  • Local development environment: http://localhost:5173
  • Deployed URL: [deployed-URL] (e.g., http://ec2-13-126-149-80.ap-south-1.compute.amazonaws.com)
  • Any other future deployed URLs.

Steps to Reproduce:

1. Run the API locally with the current CORS settings.
2. Try to access the API from the deployed front-end environment.
3. Observe the CORS error.

Proposed Solution:

• Modify the CORS configuration to allow requests from multiple origins:
  • http://localhost:5173
  • https://deployed-url.com (replace with actual deployed URL)
• Alternatively, consider allowing all origins (*) temporarily or using a wildcard for similar subdomains (https://*.your-domain.com).

Priority: High

This is blocking the full functionality of the deployed front-end.

assign it under gssoc ext level 3

[abhishekraoas]

Now you can work on it

[geetanjalidubey9]

pls assign this to me

[abhishekraoas]

pls assign this to me

This issue has already been assigned. you can work on the other components

[rishyym0927]

@abhishekraoas you did not attach any labels to my closed pr. So in leaderboard I did not get any scores. This is very demotivating

[rishyym0927]

@abhishekraoas please add the labels in closed pr

[abhishekraoas]

Mention issue id