The “two forward slashes” are a common shorthand for “request the referenced resource using whatever protocol is being used to load the current page”. Best known as “protocol relative URLs”, they are particularly useful when elements — such as the JS file in your example — could be served and/or requested from either a http … Read more
Windows 10 users: Repair is only in the Control Panel, not in the Add Remove programs app. I typically run appwiz.cpl to launch the old control panel applet and run repair from there. Windows 7 and 8.1: After going to Add/Remove Programs and choosing the “Repair” option on IIS Express, the certificate has been reinstalled … Read more
The first thing you need to do is to set the level of verification. Such levels is not so much: ALLOW_ALL_HOSTNAME_VERIFIER BROWSER_COMPATIBLE_HOSTNAME_VERIFIER STRICT_HOSTNAME_VERIFIER Although the method setHostnameVerifier() is obsolete for new library apache, but for version in Android SDK is normal. And so we take ALLOW_ALL_HOSTNAME_VERIFIER and set it in the method factory SSLSocketFactory.setHostnameVerifier(). Next, … Read more
Note: While this solution may have worked in some browsers when it was written in 2014, it no longer works. Navigating or redirecting to an HTTP URL in an iframe embedded in an HTTPS page is not permitted by modern browsers, even if the frame started out with an HTTPS URL. The best solution I … Read more
This is a response I got from their Premium Services Hello, This is actually a issue with the way SSL validates names containing a period, ‘.’, > character. We’ve documented this behavior here: http://docs.amazonwebservices.com/AmazonS3/latest/dev/BucketRestrictions.html The only straight-forward fix for this is to use a bucket name that does not contain that character. You might instead … Read more
This has not been tested but I think this should work using mod_rewrite RewriteEngine On RewriteCond %{HTTPS} on RewriteRule (.*) http://%{HTTP_HOST}%{REQUEST_URI}
Use a secure URL for your initial connection, i.e. instead of “http://” use “https://”. If the WebSocket transport is chosen, then Socket.IO should automatically use “wss://” (SSL) for the WebSocket connection too. Update: You can also try creating the connection using the ‘secure’ option: var socket = io.connect(‘https://localhost’, {secure: true});
I had the same problem – I was fetching a page from my own site, which was served over HTTPS, but curl was giving the same “SSL certificate problem” message. I worked around it by adding a -k flag to the call to allow insecure connections. curl -k https://whatever.com/script.php Edit: I discovered the root of … Read more
Security note: Disabling security checks is dangerous and should be avoided You can disable security checks globally for all requests of the default client: package main import ( “fmt” “net/http” “crypto/tls” ) func main() { http.DefaultTransport.(*http.Transport).TLSClientConfig = &tls.Config{InsecureSkipVerify: true} _, err := http.Get(“https://golang.org/”) if err != nil { fmt.Println(err) } } You can disable security … Read more
If you don’t care about checking the validity of the certificate just add the –no-check-certificate option on the wget command-line. This worked well for me. NOTE: This opens you up to man-in-the-middle (MitM) attacks, and is not recommended for anything where you care about security.