CORS related error about httptoolkit-ui HOT 2 CLOSED

If you run the official server builds in the standard way, they intentionally don't allow connections from anything but the official UI. This avoids cross-site request forgery style attacks (where a malicious website you visit communicates with local services on your machine).

By default, production builds allow connections only from app.httptoolkit.tech, which dev builds also allow various localhost URLs. This is defined here.

There's two options:

• You can run a local server in dev mode from a full checkout of the code, following the instructions in that repo
• You can run the production server release in dev mode, with OCLIF_TS_NODE=0 ./bin/run start instead of ./bin/httptoolkit-server start
  • This avoids some initial setup steps, which result in the server being considered as a production build, with the restrictions that implies
  • OCLIF_TS_NODE is required to correctly run a production build (which bundles and drops various dev-only files and dependencies) in dev mode
• You can modify the server code, and build your own production releases which trust an alternative UI URL instead.

Does that all make sense?

from httptoolkit-ui.

Thanks for the answer! I previously created my own fork of the server that disables the cors protection entirely. I don't think it's a good idea tough, hence I'm going to use your provided solution for the time being.

from httptoolkit-ui.