ddn
Posts: 2
Joined: Mon Mar 26, 2018 5:12 pm

Possibility of non-HTTPS domain?

Mon Mar 26, 2018 5:14 pm

Hi guys,

I'm wondering if there's any possibility of supporting a non-HTTPS subdomain for the API? Reason being is that Plex has a broken python/SSL implementation and can't meet the server SNI requirement. Obviously Plex has a large installed base, so it's a bit of a problem.

User avatar
zag
Site Admin
Posts: 762
Joined: Tue Oct 11, 2016 9:43 am

Re: Possibility of non-HTTPS domain?

Tue Mar 27, 2018 3:28 pm

Yeh I saw this on GitHub, I will look but to be honest the web is moving towards SSL everywhere so it really needs to be fixed client side.

Main Problem is we store the complete URL in our Database so need to provide it either as HTTP or HTTPS://

I chose HTTPS for the future, its what other metadata sites are using as well such as fanart.tv and themoviedb.org

ddn
Posts: 2
Joined: Mon Mar 26, 2018 5:12 pm

Re: Possibility of non-HTTPS domain?

Tue Mar 27, 2018 3:34 pm

I hear you and you're absolutely right.

That said, if there was a non-https subdomain, I would just write a parser to rewrite the URLs in the scanner.

I'm really surprised that this is still an issue in Plex, we're takling about something that was fixed around 5 years ago in python, and they're still including ancient libraries with the PMS distribution. I know themoviedb also requires SNI, so I'm not sure why it isn't breaking in Plex, unless it's because they intercept and do the caching, which as I understand it they do for the major metadata sites.

edalex
Posts: 87
Joined: Fri Mar 03, 2017 6:45 pm

Re: Possibility of non-HTTPS domain?

Tue Mar 27, 2018 8:42 pm

Agreed with topic starter.
Honestly, I can't even load neither site nor plugin from my Ice Age HTPC :)

Return to “Developers”