# Server-side improvements for wr.fi raw artifact fetch compatibility
The issue does **not** look like “wr.fi is unreadable” in general. In this environment, the creation page loads, but the raw artifact URL fails with an odd `Failed to fetch ...: (400) OK` message. That points more toward a response-shape / proxy / header incompatibility on the artifact path than a general routing problem.
## What likely causes it
1. **Proxy/CDN edge response mismatch**
- `(400) OK` suggests one layer may be surfacing a 400-class failure while another still labels the response “OK.”
- This often happ
content.txt