[FIXES]: #234 and #235

[BUZZARDGTA]

Basically you where doing a lookup on the different possible Errors possible, while I am saying: "Oh, it's not 300 or 200? Fine then it's an error."

I'm sure you will cringe me for my ui.js code, but I tried my best to works with your (imo outdated code for this new algorythm) to make it working on your actual core.

Feel free to change the code as you prefer it, I've just put this here because it contains a fix for both of these issues.

[BUZZARDGTA]

Okay while scanning my huge database with this pull request, I've noticed that the "Errors" contains a problem, basically almost or all urls have been displayed in the UI as "Errors", the "Errors" counter itself is fine.
I know exactly what's the issue and how to fix it, it's my ui.js that contains default Errors.
I've tought about a solution where i'd keep using your old source code but creates an Errors flag: "STATUS.DOWN_OTHER" or something like that. It will be pretty cool normally since it's gonna match the previous source codes using the switch js function.

But I have really big troubles to work with the STATUS.JS as they are just a list of static const, I will probably ends up by removing it completely at some points

Anyways, gtg work for now :D

[BUZZARDGTA]

Fixed, I have pretty much reduced a lot from the file status.js, not sure how you will like it or not.
I basically made it 4 dedicated modes now instead of custom error codes like you did, now it's:

• OK
• REDIRECTION
• NOT_OK
• UNKNOWN

Note: I have removed the feature that scans on "GET" after "HEAD" failed. (it was not implemented from you anyways); and since now we anyways only scan using "GET" in the first place, that feature doesn't even make sense to keep anymore.

[BUZZARDGTA]

Little hotfix because I'm a clown 🤡