mirror of
https://github.com/stablyai/orca.git
synced 2026-11-17 03:15:01 +00:00
chatgpt.com answers every request from Cloudflare Workers' egress IPs with a 403 "Unable to load site" HTML page, whatever the token (verified from a throwaway Worker; the same request from elsewhere gets a normal 401). Codex via the Orca account goes through the Worker egress proxy, so it got that page on /responses and /wham/usage: "Working…" without an answer, and /status had no limits. The proxy now recognises a provider edge's own refusal (403, text/html, server: cloudflare) on routes that define an answer for it, logs egress_upstream_blocked, and answers Codex in ChatGPT's error shape so Codex prints a plain message. The block says nothing about the credential: no status hook, so no refresh and no revoke. This doesn't make Codex work; routing chatgpt.com around the Worker is a separate decision.