Config input
- Input chars
- 167 / 40960
- Mock mode
- HTTP response
- Status policy
- Resolve every status below 500
Build a request, choose allowlisted interceptor actions, mock the response lifecycle and see whether Axios would resolve or reject. The page stays client-side, masks secret-like values and never calls the entered URL.
Change method, baseURL, URL, params, headers, body, timeout, validateStatus and mock output. The simulator creates a timeline and a copyable Axios snippet from the safe model.
Bearer token masking plus validateStatus that resolves a 404 response for API-level error handling.
Run the simulator to see no-network diagnostics, interceptor timeline, resolved config and a copyable Axios snippet.
Axios config often looks like plumbing, but it decides whether callers see then or catch, whether secrets leak into logs, how timeouts behave and how request interceptors modify headers and params. This simulator makes those decisions visible before code review.
const client = axios.create({ baseURL, timeout, headers });validateStatus: (status) => status < 500
The worker never fetches the URL. It models the request and mock output so public usage stays safe.
Interceptor behavior is represented as curated actions, not arbitrary JavaScript pasted by the user.
The result calls out when 4xx or 5xx responses would resolve instead of reject.
No. It only simulates the config and mock response lifecycle in the browser worker.
Do not paste real secrets. Secret-like keys and values are masked, but the safe workflow is to use placeholders.
A public page cannot safely run arbitrary interceptor code. The allowlist keeps the behavior explainable and reviewable.
No. Use it for review and education, then verify real CORS, auth, retries and response parsing in your application test suite.