Ask for credentials when configured bytebin returns HTTP 401 (Unauthorized)

[BrainStone]

Alright this is a feature request meant to allow a custom bytebin to require authentification for security. Primarily if that bytebin connected directly to the storage and generates the data itself.

Now when the bytebin URL returns the HTTP status code 401 the editor (and possibly verbose and tree viewer too) should ask the user for credentials. After they were provided the URL is requested again this time with the credentials. When the data is saved the credentials should be provided as well.

I'm not sure what's the best way to send the credentials, as the connection may be unsecured.

Also ideally there's a checkbox that stores the credentials for that specific bytebin URL. Not for others as the same bytebin might require authentification for some URLs but not for others.

---

The underlying idea is that I create an addon for LuckPerms that runs a faked Bytebin. So that when a specific URL is requested it sends the permission data directly instead of uploading it to a separate server. Also when the editor saves data it is applied directly, if the auth is correct.
However it still needs to function as a normal bytebin for verbose and tree. That's why normal URLs will not require auth.

As a convinciece feature it would be awesome if the editor had a configuration option to always open a specific bytebin URL by default (if none is given).

[lucko]

My opinion is that this isn't something that we should officially support - the stakes are much higher if we get something wrong security wise, and I also don't think it's likely to be a popular feature & therefore not worth spending time supporting.