| FILED ET | TICKER | COMPANY | INSIDER | ROLE | TYPE | SIDE | SHARES | PRICE | VALUE | ΔOWN |
|---|
| FILED ET | TICKER | COMPANY | INSIDER | ROLE | TYPE | SIDE | SHARES | PRICE | VALUE | ΔOWN |
|---|
EDGAR's filing feed (www.sec.gov) does not send CORS headers, so requests run
through an automatic failover chain: direct → your proxy → local proxy (auto-detected on
127.0.0.1:8743) → public relays. Note: SEC currently blocks the public relays
(verified 2026-06-12), so in practice a relay you run is required — the local Python one below
is found automatically when running. data.sec.gov is CORS-open and always fetched
directly. All traffic flows through one function (edgarFetch):
SEC fair-access rules ask automated clients to identify themselves via a User-Agent header. Browsers can't send one cross-origin (SEC's edge 403s the preflight — verified), so your proxy should. Both recipes below do, and only allow sec.gov URLs.
Settings are in-memory only (cleared on reload). To persist, edit
CONFIG.PROXY_PREFIX at the top of the script in this file.