<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Https on Rowanto Luo</title><link>https://log.rowanto.com/categories/https/</link><description>Recent content in Https on Rowanto Luo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sat, 21 Mar 2015 09:11:56 +0000</lastBuildDate><atom:link href="https://log.rowanto.com/categories/https/index.xml" rel="self" type="application/rss+xml"/><item><title>Java 8 - Turning off SSL Certificate Check</title><link>https://log.rowanto.com/posts/java-8-turning-off-ssl-certificate-check/</link><pubDate>Sat, 21 Mar 2015 09:11:56 +0000</pubDate><guid>https://log.rowanto.com/posts/java-8-turning-off-ssl-certificate-check/</guid><description>
&lt;p&gt;There&amp;rsquo;s usually no good reason to turn off SSL certificate check. So this is actually wrong in many ways, but maybe we&amp;rsquo;re still developing in an isolated dev environment and somehow the dev machine of another application you&amp;rsquo;re depending on only allows SSL connection even though it doesn&amp;rsquo;t have a valid certificate. The correct solution is actually to self sign a certificate or add it in the system, so that if your application go live, you will still have ssl certificate check turned on. If not, you might forgot to turn the ssl certificate check back on when launching the stuff and it will be bad. So, use this on your own risk.&lt;/p&gt;</description></item></channel></rss>