Replies: 1 comment
-
Hi @Dinth thanks for your input! The correct allowGET (and similar) parameters really depend on the specific application or API in use. Unfortunately, there is no “one-size-fits-all” regular expression that will work for every service—each app can use different endpoints, and sometimes these change with updates. Maintaining a constantly up-to-date list of all popular apps and their required settings is simply not possible and won’t be provided—this would require far more time than is practical for any open source project. That’s why the documentation explains how to figure out the correct permissions yourself: https://github.com/wollomatic/socket-proxy#examining-the-api-calls-of-the-client-application With this approach, everyone can easily see exactly which endpoints are being called, and then lock down the permissions as needed for their own setup. Of course, a collection of working examples in the Wiki would be very welcome! Best regards! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi. All the examples i can find (both in your documentation and by searching github for other people docker compose files) show allowGET (and other allow... paremeters) formated like this:
allowGET=/v1\..{1,2}/(version|containers/.*|events.*)
but while this works for Traefik, this regexp doesnt work for many of the services: just to mention WUD, Uptime Kuma, Homepage.
for those ones
allowGET=/(version|containers/.*|events.*)
seems to be working fine. It would be nice to have the documentation updated with a regexp for those services to save other people troubleshooting
Beta Was this translation helpful? Give feedback.
All reactions