- Moderator
- #131
Rerurn:http://thetvdb.com/api/<apikey>/updates/updates_week.zip
Code:
{
status: "redirect",
data: null,
message: "function not found"
}
Rerurn:http://thetvdb.com/api/<apikey>/updates/updates_week.zip
{
status: "redirect",
data: null,
message: "function not found"
}
C#:ServicePointManager.SecurityProtocol = (SecurityProtocolType)0xc00;
Best practic - use TLS 1.2 and 1.3 TLS 1.0 outdate like SSL...Keep in mind that 0xc00 is only needed on .NET 4.0, and that in .NET 4.5 you can refer to it as Tls12, which in .NET 4.6.2+ is made default now (or .NET Core).
Problem is that when you use = and not |= that you kill off TLS 1.0 and 1.1 support, which some servers still require if they are not configured to handle TLS 1.2-Only connections. Otherwise Forward-Secrecy is not used and then connection is sometimes killed off.
Hi everyone, another update for you. We’ve started a complete list of known issues that we’re working on fixes for, as well as issues that we have released fixes for already. You can see the full list here: https://forums.thetvdb.com/viewtopic.php?f=122&t=60239
We will continue to update this as new releases are pushed out. Again, we can’t say it enough — thank you so much for your patience as we work through these.
About 4.0 and 4.6.2+, We discussed this, the test code is here: https://forum.team-mediaportal.com/posts/1256420/Keep in mind that 0xc00 is only needed on .NET 4.0, and that in .NET 4.5 you can refer to it as Tls12, which in .NET 4.6.2+ is made default now (or .NET Core).
ServicePointManager.SecurityProtocol = (SecurityProtocolType)0xc00;
Best practic - use TLS 1.2 and 1.3 TLS 1.0 outdate like SSL...