Skip to content

EUrouter: re-add once it allows browser calls via CORS (removed for now) #32

Description

@jstet

EUrouter only allows its own site via CORS, so the browser can't call it directly and requests go through the /api/eurouter/v1 proxy in serve.js. That means the user's API key, prompts and generated questions pass through the formulaid host. Nothing is stored there, but every request path is logged.

Checked 2026-09-25 with Origin: https://formulaid.example.org:

  • OPTIONS /api/v1/chat/completions → 204, but access-control-allow-origin: https://www.eurouter.ai
  • POST and GET /api/v1/models → same, with only https://www.eurouter.ai allowed

Options:

  1. Ask EUrouter to allow formulaid's production origin (or * for /api/v1, as OpenRouter does). Then switch baseUrl to https://api.eurouter.ai/api/v1 and remove the proxy. Together with the OpenRouter change, serve.js could go entirely and the static build could be hosted on any static host.
  2. Keep the proxy and make it explicit: say in the provider selection / privacy text that EUrouter requests are relayed through the formulaid server without being stored, stop logging proxied paths, and don't forward cookies.

Option 1 is preferred; option 2 applies until EUrouter responds.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions