Documentation Index
Fetch the complete documentation index at: https://docs.utnor.com/llms.txt
Use this file to discover all available pages before exploring further.
Let’s keep this simple.
Have you ever tested a feature and thought, “Okay… but what happens on the client side if the server suddenly says 403?”Or 404. Or 500. Or anything that isn’t a clean 200. Usually, we fake it. We hardcode an error, mock a response, or tweak some condition and move on. It works — but it never quite feels real. Because the truth is, clients behave differently when the network actually responds. Browsers, SDKs, UI frameworks, retry logic — they all react to real HTTP status codes in their own ways. That’s exactly what is for.
What Custom Status is (and isn’t)
Custom Status is a single-purpose HTTP utility.You ask for a status code, and the server responds with that exact status. Nothing more.
- No response body
- No conditional logic
- No interpretation of intent
- No hidden behavior
- The request is received
- The requested status code is resolved
- The response is returned
Why it exists
This tool exists purely to help you observe client-side behavior. By keeping things intentionally minimal, Custom Status stays out of the way so you can focus on what actually matters: how your client reacts when the network says “no”, “retry”, or “something went wrong”. What you see is what your client gets.Naming and identity
On the platform, the tool appears as Custom Status.In technical references, paths, and examples, it’s identified as
status.
Both names point to the same tool and produce the exact same behavior.
Consistency by design
Custom Status is intentionally narrow in scope. There are no modes, flags, or environment-specific variations. If you request the same status code today or later, the response remains the same. Because it doesn’t rely on internal state, configuration, or stored context, it behaves identically whether it’s hosted or self-hosted. The rules never change.In short
Custom Status is not a framework, mock server, or testing suite. It’s a small, focused utility with a clearly defined job:Return the status code you ask for — exactly as requested.The behavior you observe is the client’s, not the tool’s.