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
I apologize in advance if the following discussion weirds someone out, feels pointless - a waste of time or any kittens are harmed.
Possibly important context: I don't know coding/programming, I'm that paranoid guy with setup exposed to internet for convenience with 10 different layers of authentication, yet actively looking to add more.
I'll start by explaining my current setup:
2 domains
domain 1: behind authelia oidc integrated with cloudflared
domain 2: public use, exclusive for sharing files or allowing family n friends to watch/dl some content remotely (this domain is what interests us for this discussion)
For domain 2, in nginx I have specified some paths, and rejected others, of which I have specified /public/* as is. That is to say, all paths under /public/* can be accessed. While looking into the features of the app, the logs generated and the connections made to understand and specify the paths and fix errors due to dumb changes from the previous config (defined for the older filebrowser), I realized /public/* path has many more subpaths and they serve important purpose.
I would like to know them all or at least a way to get to know them all, and choose the paths that I need, and actively block the rest on publicly accessible front.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello there.
I apologize in advance if the following discussion weirds someone out, feels pointless - a waste of time or any kittens are harmed.
Possibly important context: I don't know coding/programming, I'm that paranoid guy with setup exposed to internet for convenience with 10 different layers of authentication, yet actively looking to add more.
I'll start by explaining my current setup:
For domain 2, in nginx I have specified some paths, and rejected others, of which I have specified /public/* as is. That is to say, all paths under /public/* can be accessed. While looking into the features of the app, the logs generated and the connections made to understand and specify the paths and fix errors due to dumb changes from the previous config (defined for the older filebrowser), I realized /public/* path has many more subpaths and they serve important purpose.
I would like to know them all or at least a way to get to know them all, and choose the paths that I need, and actively block the rest on publicly accessible front.
All reactions