Shield reporting http on https connections for directplay

[Edrock200 53]

Have an interesting issue. I have emby in on a cloud server in a container behind an SSL reverse proxy in another container. The reverse proxy talks to emby on the decrypt port internally (8096) and ssl 443 out to the shield client. Port 80 is published for decrypt but redirects to ssl 443.

 

When I direct play on the shield and click stats for nerds, it shows connect type as http. If I lower the bandwidth to force transcode it shows connect type hls. To ensure it wasn't some issue with port 80 redirect, I manually added a server with an https string and port specified as 443. Same result. I don't publish the internal emby ports (8096 or 8920) to the host ip so it's not possible for clients to connect to those.

 

When I do the same test via web browser to the same url, both directplay and transcode show https/hls. I suspect the shield is pulling the connect status from the emby server vs the client itself, since the server is handing http to the reverse proxy, but I can't be sure.

Is this intended behavior, a bug or something else?

[ebr 16184]

Hi.  That is just indicating the general protocol by which the item is being delivered and isn't being specific as to whether or not it is over SSL.

[Edrock200 53]

Interestinf because the web client specifically says https. Shield just says http. Shield changes to hls when transcoding.

[ebr 16184]

5 minutes ago, Edrock200 said:

web client specifically says https

Exactly where?

[Edrock200 53]

Under stats for nerds. Please see attached.

[ebr 16184]

Okay, thanks.  We'll improve the display in the app.

[Edrock200 53]

Thanks! It seems like it has the ability to detect because as I mention when transcoding the shield shows hls. It's only directplay that it shows http. Thanks again!