<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Has Opera changed how it handles invalid security certs?]]></title><description><![CDATA[<p dir="auto">Currently using opera 43 I cannot access a webpage that I use internally for work since the cert is invalid. I know the server is internal and even if the connection was compromised it would not effect me since the data we enter there is not sensitive.</p>
<p dir="auto">I understand that this could be a security issue for people who may not understand the risks but I think that these problems occur for other reasons and blocking access to a site completely because of this may be overkill? If there is an easy way to get opera to provide an exception for this server could anyone point me in the right direction?</p>
]]></description><link>https://forums.opera.com/topic/19440/has-opera-changed-how-it-handles-invalid-security-certs</link><generator>RSS for Node</generator><lastBuildDate>Sat, 18 Apr 2026 08:51:34 GMT</lastBuildDate><atom:link href="https://forums.opera.com/topic/19440.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 23 Feb 2017 16:34:25 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Has Opera changed how it handles invalid security certs? on Tue, 24 Oct 2017 09:31:02 GMT]]></title><description><![CDATA[<p dir="auto">See <a href="https://forums.opera.com/topic/19188/updated-to-43-can-no-longer-continue-anyway-on-bad-certs">here</a>.<br />
<img src="https://forums.opera.com/assets/plugins/nodebb-plugin-emoji/emoji/emoji-one/1f642.png?v=f58hvca1lju" class="not-responsive emoji emoji-emoji-one emoji--slightly_smiling_face" title=":)" alt="🙂" /></p>
]]></description><link>https://forums.opera.com/post/115736</link><guid isPermaLink="true">https://forums.opera.com/post/115736</guid><dc:creator><![CDATA[[[global:former_user]]]]></dc:creator><pubDate>Tue, 24 Oct 2017 09:31:02 GMT</pubDate></item></channel></rss>