No, because the problem is not with AIR, it is with either the site's certificate, or with the configuration of the client's machine or network that prevents the certificate revocation checking from working correctly. AIR does not let you do potentially unsafe or damaging things to the machine it is installed on, which is a good thing. The customer has configured their machine to not allow connections to secure sites that the certificate revocation check fails on. If AIR allowed you to circumvent this, it would be a huge security hole. Which of course would be splashed all over all the security and computer media web sites and blogs, and then you wouldn't be able to get an AIR application installed anywhere.
That said, I would much prefer that AIR send back a more useable error, so that I can trap it correctly and display an explanation window to the user so they can then make the decision if they want to change their configuration. Given the number of things that can cause an http / https call to fail, trying to display all the possible reasons would be a waste of time.
Mark
