Just had the same problem. Tumblr updated their Encryption policies. If you’re a theme developer and you’d like to ensure your themes support HTTPS, make sure that any externally hosted resources, such as Cascading Style Sheets (CSS) or Javascript files, and even images, are served using HTTPS. As we now know that Tumblr requires that we … Read more
Option 1: Disable the warning (useful for dev) From your question I’m guessing you are doing this in development as you are using a self signed certificate for SSL communication. If that’s the case, add as an environment variable wherever you are running node or running node directly with This instructs Node to allow untrusted … Read more
if you’re using a self signed certificate on the server, you can use: but be aware that then it’s no better than using non SSL connection to the server, as your communication won’t be secure anymore, enabling all sorts of man in the middle attacks. Though my advice to you is to download the .pem from the … Read more
i m trying to send post request to webservice.. when i add special character @ in parameter it is coverted to %40.i have checked server side..they are getting %40 instead of @. can any one help me?? here is my code.. i have also tried this method to prevent my parameter from encoding. but it … Read more
TLS/SSL (The S in HTTPS) guarantees that there are no eavesdroppers between you and the server you are contacting, i.e. no proxies. Normally, you use CONNECT to open up a TCP connection through the proxy. In this case, the proxy will not be able to cache, read, or modify any requests/responses, and therefore be rather useless. If … Read more
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. Edit: I discovered the root of the problem. I was using … Read more
To permanently accept a specific certificate Try http.sslCAPath or http.sslCAInfo. Adam Spiers’s answer gives some great examples. This is the most secure solution to the question. To disable TLS/SSL verification for a single git command try passing -c to git with the proper config variable, or use Flow’s answer: To disable SSL verification for a … Read more
Update: Although this answer has been accepted a few years ago, note that its approach is now recommended against by the Apache documentation. Use a Redirect instead. See this answer.
jww is right — you’re referencing the wrong intermediate certificate. As you have been issued with a SHA256 certificate, you will need the SHA256 intermediate. You can grab it from here: http://secure2.alphassl.com/cacert/gsalphasha2g2r1.crt