Learn
History for this tool
The most recent data you entered in this tool, stored only in this browser.
Save what you type here, in this browser? Your work would go into this browser's local storage, so a refresh or a trip to another tool does not wipe it. You also get a short list of previous entries under the form, each one restorable with a click. Nothing is ever uploaded, and there is no account.
Being straight about the trade-off: anything kept there can be read by anyone who can use this browser profile, and by any script that later runs on this site. A tool page can hold a private key, a password or a signed token. Saving is convenient; it is not private.
Saved on this device
Your inputs and history are stored locally.
Not saved
This page forgets your work when you leave it.
About this tool
A searchable reference of HTTP response status codes, what each one means and when a server should return it.Questions
- When should I return 401 instead of 403?
401means the request lacks valid authentication credentials for the resource; a client may need to authenticate or renew them.403means the server understood the request but refuses it. Do not assume a403always means the client was successfully authenticated; check your application’s access rules.- Does 200 always mean success?
- For a GET, usually. For an API, a 200 carrying an error object is a common and unhelpful habit. Prefer a status code that matches the outcome.