SecurityProtocol and 500 server error
I'm confirming on the ServicePointManager...
https://docs.microsoft.com/en-us/dotnet/api/system.net.servicepointmanager?view=netframework-4.7.2
That if I use this with an HttpWebRequest, it will require one of these protocols:
When we send XML to the client, it is erroring with a 500 server error, and I suspect it is because, as I was just informed, that they haven't configured the TLS12 yet.
If I have that protocol set prior to sending our HttpWebRequest, will it cause a 500 server error if they don't have it configured?
Thanks!
https://docs.microsoft.com/en-us/dotnet/api/system.net.servicepointmanager?view=netframework-4.7.2
That if I use this with an HttpWebRequest, it will require one of these protocols:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 Or System.Net.SecurityProtocolType.Ssl3 Or System.Net.SecurityProtocolType.TlsWhen we send XML to the client, it is erroring with a 500 server error, and I suspect it is because, as I was just informed, that they haven't configured the TLS12 yet.
If I have that protocol set prior to sending our HttpWebRequest, will it cause a 500 server error if they don't have it configured?
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Would that be like the above?
And it would just be determined which is used on the end we are sending to, but not our end? We'd still require they send it using encryption? Or how might that work?