The API endpoints:
Example: https://api.tvmaze.com/lookup/shows?tvrage=24493
Example: https://api.tvmaze.com/lookup/shows?thetvdb=81189
Example: https://api.tvmaze.com/lookup/shows?imdb=tt0944947
all redirect to the non-SSL http:// endpoints. http://api.tvmaze.com/shows/...
This defeats the purpose of HTTPS.
That's not great indeed, but unfortunately I can't fix this in our current nginx version (it rewrites relative redirect URLs to absolute ones, which is not compatible with our caching architecture). Will fix this when we can; for now you'll have to manually parse the response's "Location" header if it must return HTTPS.
