HTTP 407 — Proxy Authentication Required
HTTP 407 is 401 as spoken by proxies: an intermediary demands credentials before forwarding the request, and the Proxy-Authenticate header says which scheme it expects.
When 407 shows up
- Corporate proxies requiring authentication for outbound traffic.
- Crawlers configured through authenticated proxy pools.
Mocking a 407 response
A response with this status can be faked end to end with a local mock rule — no backend changes needed. The configuration below mirrors the rule fields the ApiSimul editor uses (method, path, status, delay in milliseconds, response body):
{
"method": "GET",
"path": "/api/external",
"status": 407,
"delay": 220,
"enabled": true,
"body": null
}Dynamic placeholders such as {{random.name}}, {{string.uuid}} or {{number.int 1 100}} can appear inside the body to vary each response, which keeps client-side list rendering and retry logic honest during development.
Frequently asked questions
What does HTTP 407 mean?
The proxy in the path needs credentials before it will forward the request. The client supplies Proxy-Authorization and retries.
How can I test a 407 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 407. The example configuration above returns this response after the listed delay, so the client exercises its 407 handling exactly as it would against a live server.
Related status codes
Need the response in your own project? Spin up rules for any status with the ApiSimul mock server, or browse every status code page.