Search Issue Tracker
Fixed in 2018.2.X
Votes
8
Found in
5.3.5p1
Issue ID
842830
Regression
No
UnityWebRequest does not indicate that a SSL certificate is invalid
Steps to reproduce:
1. Open the project.
2. Hit play
3. Notice there is a webpage output to the Debug.Log which includes:
<div id="content">
<h1 style="font-size: 12vw;">
expired.<br>badssl.com
</h1>
</div>
Reproduced with: 5.3.6p7, 5.4.2f1, 5.5.0b8
Expected: UnityWebRequest somehow recognises that the SSL certificate is invalid, e.g. with an error, or failing in some way
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
nikki_sh
Jun 07, 2017 02:57
@NPSKIR yes, the "- No way to just say "trust self-signed" certificates " bothers us
npskirk
Feb 20, 2017 21:40
Overall it just seems like SSL/TLS was not even considered in the design of the UnityWebRequest API.
Problems:
- No way to simply have a certificate as an asset of the project and then trust that certificate when making HTTPS requests
- No way to have your own signing certificates that establish a chain of trust that you make yourself
- No way to just say "trust self-signed" certificates
- SSL-related errors are all "unknown error"
There are dozens of gripes about this on the forums -- these problems affect real uses cases in both development and production.