[GH-ISSUE #5804] Opinion / Discussion: Cross-Origin API Issues in Hoppscotch (Web Version) #2269

New issue

Open

opened 2026-03-16 23:47:59 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 23:47:59 +03:00

Owner

Originally created by @pinkal26022005 on GitHub (Jan 26, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5804

I’m facing an issue with cross-origin API requests not working in the Hoppscotch web API testing tool, and I’d like to get input from the developer/community perspective.

My setup:

Backend APIs are running on my macOS machine (my Mac acts as the server).

I generate a frontend build and serve it through NGINX, mapped to a custom domain.

From the Hoppscotch web app, when I try to hit cross-origin APIs, the requests fail due to browser CORS restrictions.

Currently, this only works if I use a browser extension or proxy, which is not ideal for all use cases.

My questions to the community/developers:

Is there any supported or recommended way to handle cross-origin API requests in the Hoppscotch web version without relying on a browser extension or proxy?

Are there best practices (server-side CORS configuration, reverse proxy setup, or Hoppscotch-specific features) that can help in this scenario?

Is this limitation inherent to browser security, or are there plans/workarounds within Hoppscotch to improve this experience?

Originally created by @pinkal26022005 on GitHub (Jan 26, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5804 I’m facing an issue with cross-origin API requests not working in the Hoppscotch web API testing tool, and I’d like to get input from the developer/community perspective. My setup: Backend APIs are running on my macOS machine (my Mac acts as the server). I generate a frontend build and serve it through NGINX, mapped to a custom domain. From the Hoppscotch web app, when I try to hit cross-origin APIs, the requests fail due to browser CORS restrictions. Currently, this only works if I use a browser extension or proxy, which is not ideal for all use cases. My questions to the community/developers: Is there any supported or recommended way to handle cross-origin API requests in the Hoppscotch web version without relying on a browser extension or proxy? Are there best practices (server-side CORS configuration, reverse proxy setup, or Hoppscotch-specific features) that can help in this scenario? Is this limitation inherent to browser security, or are there plans/workarounds within Hoppscotch to improve this experience?