How to disable Chrome HSTS permanently for a subdomain
You can type thisisunsafe anywhere on the Google Chrome warning page and it will load it without warning. No joke.
You can type thisisunsafe anywhere on the Google Chrome warning page and it will load it without warning. No joke.
Revisiting this. Here’s a great online tool recently built: https://www.ssllabs.com/ssldb/analyze.html e.g. Paypal: https://www.ssllabs.com/ssldb/analyze.html?d=https://paypal.com There are more details when you drill into a specific server. When this question was asked I remember I was looking for resources I could use to build a tool that would automatically check if ssl was configured “properly” for a given … Read more
Ok, found the solution to the cookie problem. See XHR specs, jQuery docs and StackOverflow. The solution to have the cookies sent when switching protocol and/or subdomain is to set the withCredentials property to true. E.g. (using jQuery) $.ajax( { /* Setup the call */ xhrFields: { withCredentials: true } });
Use set_debug_output. http = Net::HTTP.new(url.host, url.port) http.set_debug_output($stdout) # Logger.new(“foo.log”) works too That and more in http://github.com/augustl/net-http-cheat-sheet 🙂
I had the same problem as @User39604, and had to follow VARIOUS advices. Since he doesnt remember the precise path he followed, let me list my path: check if you have SSL YES using <?php echo phpinfo();?> if necessary A. enable ssl on apache sudo a2enmod ssl B. install openssl sudo apt-get install openssl C. … Read more
I got a solution from this article Following are the steps for Microsoft edge – Go to Edge browser and type following statement in address bar. edge://net-internals/#hsts Scroll all the way down to the section below and enter “localhost”, then click “Delete”.
If anybody wants to make it run on local machine then adding this to server REPO/.hg/hgrc will do the work: [web] allow_push = * push_ssl = false as described at this site.
You should never share your private key. You should consider the key you posted here compromised and generate a new key and signing request. You have a certificate request and not an actual signed certificate. You provide the request (‘CSR’) to the signing party. They use that request to create a signed certificate (‘CRT’) which … Read more
I was able to solve this based on an answer from Ask Different. In short, closing Safari, then running the commands below, worked. sudo killall nsurlstoraged rm -f ~/Library/Cookies/HSTS.plist launchctl start /System/Library/LaunchAgents/com.apple.nsurlstoraged.plist Restarting Safari after running that and trying to go to http://localhost:3000 solved the problem and did not redirect to to https. Hopefully this … Read more
I also came across the same error. In my case I had to supply additional CA certificates in the verification chain. And instead of supplying the certificate and the key in separate files, I combined them in a .pem file. However, when you do this, the order of the key and the certificate plus the … Read more