The connection is encrypted even if the SSL certificate isn’t valid (expired, snake-oil, untrusted CA, etc.). The SSL certificate validation just makes sure you’re connecting to the folks you think you’re connecting to. Encryption doesn’t do you any good if the folks decrypting your data are crackers instead of PayPal.
Thanks,Bruno for giving me heads up on Common Name and Subject Alternative Name. As we figured out certificate was generated with CN with DNS name of network and asked for regeneration of new certificate with Subject Alternative Name entry i.e. san=ip:10.0.0.1. which is the actual solution. But, we managed to find out a workaround with … Read more
You have two practical options: Stand up your own CA. You can do it with OpenSSL and there’s a lot of Google info out there. Keep using your self-signed cert, but add the public key to your trusted certs in the browser. If you’re in an Active Directory domain, this can be done automatically with … Read more
The requested URL might show up in Web server logs and browser history/bookmarks which is not a good thing.
Why is HTTPS required? To verify whether the website is authenticated/certified or not (uncertified websites can do evil things). An authenticated website has a unique personal certificate purchased from one of the CA’s. Who are CA’s (Certificate Authorities)? CA’s are globally trusted companies like GoDaddy, GeoTrust, VeriSign etc who provide digital certificates to the websites. … Read more
location.protocol should do it for you. (as in: if (location.protocol === ‘https:’) { // page is secure } )
Non-privileged user (not root) can’t open a listening socket on ports below 1024. Check this Give Safe User Permission To Use Port 80 Remember, we do NOT want to run your applications as the root user, but there is a hitch: your safe user does not have permission to use the default HTTP port (80). … Read more
You can do it in code: Global.asax.cs protected void Application_BeginRequest(){ if (!Context.Request.IsSecureConnection) Response.Redirect(Context.Request.Url.ToString().Replace(“http:”, “https:”)); } Or You could add the same code to an action filter: public class SSLFilter : ActionFilterAttribute { public override void OnActionExecuting(ActionExecutingContext filterContext){ if (!filterContext.HttpContext.Request.IsSecureConnection){ var url = filterContext.HttpContext.Request.Url.ToString().Replace(“http:”, “https:”); filterContext.Result = new RedirectResult(url); } } }
Warning: The following code should not be used in production because it is vulnerable to SSL attacks Probably these codes below will be helpful for you: 1.Create a HttpsTrustManager class that implements X509TrustManager: public class HttpsTrustManager implements X509TrustManager { private static TrustManager[] trustManagers; private static final X509Certificate[] _AcceptedIssuers = new X509Certificate[]{}; @Override public void checkClientTrusted( … Read more