> Is there even a use case for this for which there isn’t already a better solution? I deal with a third-party hosted webapp that enables extra when a webserve

> Is there even a use case for this for which there isn’t already a better solution? I deal with a third-party hosted webapp that enables extra when a webserver hosted on localhost is present. The local webserver exposes an API allowing the application to interact more closely with the host OS (think locally-attached devices and servers on the local network). If the locally-installed webserver isn't present the hosted app hides the extra functionality. Limiting browser access to the localhost subnet (127.0.0.1/8) would be fine to me, as a sysadmin, so long as I have the option to enable it for applications where it's desired.