User:Headquarter8302/errors


 * If you haven't figured out already, the way I wrote this guide is satirical, but it contains actual information about HTTP statuses.

Errors in FANDOM are known to be the most indescriptive errors in the whole universe of error messages, even my old Windows XP Command Prompt throws better errors than FD.

Anyways, here is some definitions to get you started on the wonderfully awful world of HTTP statuses (and errors):

HTTP 1XX
Informational messages, these are logs and tiny pieces of data to keep the server and the host happy, you could also make a trace log out of these 1XX messages. But you would never see these messages as an end user.

HTTP 2XX
Success(!) messages, these indicate that the request was received, understood, and processed without a hitch. There might be some messages that you might consider as an "error", but these actually, in fact, are not, because what counts as errors in HTTP is when there is an unexpected chain of events that lead to unexpected results, but if for example, the server knows perfectly fine that there is nothing to return to the host and there is no need to so, it would return success (HTTP 204).

Again, as an end user, you would never encounter 2XX messages.

HTTP 3XX
Redirection notices, these indicate that the location you are going to might be in another place, or that the location you are going to have a branching road. Sometimes these act as gatekeepers, telling you to use credentials or proxies to access the resource.

You would VERY RARELY encounter these in the wild.

HTTP 4XX
Client errors. That's right, all HTTP 4XX messages means that it's YOUR fault that you are not getting what you want. Commonly appearing statuses are:
 * HTTP 400. bro, wth is dis, format ur rquest correctly or i'll send a hit squad to ur house . You did something wrong with your request, a bit rarer than others, but still pretty common if you do weird stuff with the editor.
 * HTTP 403. "You shall not pass!". Your request is DENIED.
 * HTTP 404. The server knows that the thing you are looking for doesn't exist, but because your request is ambiguous (doesn't provide any other context), it also returns an ambiguous status.
 * HTTP 408. High five! Whoops, too slow! The time it took for your request to be processed by you is too long for the server to wait.
 * HTTP 429. STOP POSTING ABOUT AMONG US. I'M TIRED OF SEEING IT. IT'S ALL AMONG US. You basically soft-DoSed the server with too many requests.

HTTP 5XX
Server errors. Finally, something that you can blame FANDOM with, server errors. It's none of your fault, it's theirs. Commonly appearing statuses are:
 * HTTP 500. Remember that time when you are just using your PC fine then suddenly explorer.exe randomly crashed? Yeah, it's basically this, a generic error that nobody knew what caused it.
 * HTTP 502. Same as HTTP 502, but staff forgot to turn off secondary stuff.
 * HTTP 503. FANDOM's servers is down for some time.
 * HTTP 504. A drug cartel's middleman haven't heard anything about his boss for the last few minutes, so he wrapped the deal away. Server is functioning, but the part where they would generate a response is unresponsive (what an irony).

Custom errors
These are custom errors FANDOM implemented when there are no fitting HTTP errors:
 * Error loading data from server: Failed to connect. Ambiguous connection failure, it's neither your fault, or the server's.

And that's pretty much all you would need to know to tackle errors in FANDOM. Thank you for reading this, and I'll see you again, real soon. ~  Headquarter 83  02 c  03:11, 9 February 2022 (UTC)