You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a self-hosted solution, I would welcome to have the ability to config several credentials that need to be put in in order to use the website / API. This would also completely solve #9 on private instances.
The text was updated successfully, but these errors were encountered:
Can't said reverse-proxies handle HTTP-AUTH with a simple user/password or token?
This is quite a common approach with a lot of web-based applications and espechally when using ngnix as sanitizer for SQL queries to stop low-level skiddies and bots.
Same with rate-limiting: If I were to seriously host this, I'd propably limit the packet rate or bandwith per connection / IP to something in the ream to 10MBit/s - 100 MBit/s maximum via either the transparent proxy or some MITM "firewall" / "load-balancer" appliance [yes that is ugly but too bad big corporate IT is messy!]...
For a self-hosted solution, I would welcome to have the ability to config several credentials that need to be put in in order to use the website / API. This would also completely solve #9 on private instances.
The text was updated successfully, but these errors were encountered: