funman300
3b7a4928c9
## TLS (#11) - Self-signed cert generated at startup via rcgen (covers localhost, 127.0.0.1, fut.ea.com, utas.mob.v4.fut.ea.com); activated with TLS_ENABLED=true - Custom accept loop: tokio-rustls acceptor → hyper-util auto Builder → axum Router (no axum-server dependency — uses hyper 1.x natively) ## Replay CLI (#12) - New binary: openfut-bridge-replay <file.json|dir> [bridge-url] - Replays single capture or entire directory against Bridge - Accepts self-signed certs automatically ## Capture quality (#13, #14) - DELETE /_bridge/captures — wipe all capture files from disk - Deduplication: same method+path within 1 s is skipped (configurable constant) ## Admin UI (#21, #22, #23) - GET /_bridge/admin — embedded HTML dashboard; auto-refresh every 10 s Shows: live stats, SSE log of incoming traffic, endpoint status table, recent captures list with delete button - GET /_bridge/status — per-endpoint mapped/known/unknown status - GET /_bridge/captures/stream — SSE stream; event: capture on each request Uses tokio::sync::broadcast channel (capacity 256) in ProxyState ## Tests (#24, #25) - 9 new tests: placeholder format, full HTTP integration (health, placeholder, captures list, delete captures, status), TLS cert generation + acceptor build - Total bridge tests: 13/13 passing Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
OpenFUT Bridge
FIFA 23 integration layer and reverse-engineering proxy.
OpenFUT Bridge sits between the FIFA 23 client and the internet. It intercepts all FUT API traffic, logs every request, and routes known endpoints to OpenFUT Core. Unknown endpoints receive safe placeholder responses so the client keeps running.
What it does
- Transparent HTTP proxy — point FIFA 23 here instead of EA's servers
- Logs every request (method, path, headers, body, timestamp) to
captures/ - Maps known FUT endpoints to OpenFUT Core API calls
- Returns placeholder JSON for unknown endpoints (prevents client crashes)
- Admin API for reviewing captures and identifying unmapped routes
- Foundation for building the full FIFA 23 integration
Architecture
FIFA 23 client
│
▼
OpenFUT Bridge (port 8443)
│
├── Known route → OpenFUT Core (port 8080)
└── Unknown route → Placeholder JSON + saved to captures/
Quick Start
# Run Core first
cd ../openfut-core && cargo run
# Run Bridge
cargo run
# Or with config
CORE_URL=http://127.0.0.1:8080 BRIDGE_LISTEN_ADDR=127.0.0.1:8443 cargo run
Environment Variables
| Variable | Default | Description |
|---|---|---|
BRIDGE_LISTEN_ADDR |
127.0.0.1:8443 |
Bridge listen address |
CORE_URL |
http://127.0.0.1:8080 |
OpenFUT Core URL |
CAPTURES_DIR |
captures |
Where to save captured requests |
PLACEHOLDER_MODE |
true |
Return 200 for unknown endpoints |
Admin API
| Method | Path | Description |
|---|---|---|
GET |
/_bridge/health |
Bridge status |
GET |
/_bridge/captures |
All captured requests |
GET |
/_bridge/unknown |
Unknown endpoints only |
Reverse Engineering Workflow
- Point FIFA 23 at the Bridge (see
docs/setup-notes.mdfor proxy setup) - Start a game session
- Check
captures/or/_bridge/unknownfor new endpoints - Document the endpoint in
docs/endpoint-map.md - Add a mapping in
src/mapper.rs - Implement the Core handler
Proxy Setup (Research Notes)
See docs/setup-notes.md for notes on:
- Windows
hostsfile redirection - RPCS3 network config (PS3)
- Certificate bypass approaches
- mitmproxy integration
Development
cargo fmt
cargo clippy -- -D warnings
cargo test
License
MIT