With the new release, any changes/enhancements in URI_Path for the way media is accessed ?

[vaise 340]

I have a very locked down system with cloudflare, not just for emby, but for other systems I host also. 

I am also redirecting the video/audio streams to nginx so as to not risk a cloudflare ban.  That is being handled by the router firewall and nginx config to only listen for the redirects and nothing else..

My cloudflare WAF rules (on free plan), through trial and error when I set this up, have to allow the following for emby to operate - is there any movement on this ?  are you likely to move any of these root uri_paths to under /emby which would make it better for me.

I allow anything that starts with emby.mydomain.com/emby

I allow anything that starts with emby.mydomain.com/web

I block the root domain itself (emby.mydomain.com) - this alone stops most of the internet scanners out there - and a side affect is no users can use the web to access emby (unless they add /web) - which I direct them to do when testing only - I want all users to use an emby app.

That is ideally all I would like to allow, but to make emby 'work', I also have to allow the following on the root domain (emby.mydomian.com) :

/socket

/system/info/public

/Sessions/Capabilities/Full

/DisplayPreferences/usersettings

/embywebsocket

/favicon.ico

/LiveTv/Channels

/Persons

/Artists

/System/Endpoint

/Tags

/ItemTypes

/Localization/cultures

/System/Info/Public

/Shows/NextUp

Then, I also find I have to allow uri_paths that start with the below (as they are variable under there) :

/Sync/

/Sessions/

/Users/

/Items/

/Videos/

Has any of the above been moved to under /emby ?  That would be great.

 

[Luke 42077]

Hi, not that I can think of but I think it’s inevitable that you’ll find one or two