<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TLS on Eknix — Web security &amp; performance for the enterprise</title><link>https://www.eknix.com/tags/tls/</link><description>Recent content in TLS on Eknix — Web security &amp; performance for the enterprise</description><generator>Hugo</generator><language>en-us</language><copyright>© {year} EKNIX LTD. All rights reserved.</copyright><lastBuildDate>Tue, 15 Jul 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.eknix.com/tags/tls/index.xml" rel="self" type="application/rss+xml"/><item><title>CDN to Origin Certificates: Your Own CA with OpenSSL</title><link>https://www.eknix.com/blog/cdn-to-origin-certificates/</link><pubDate>Tue, 15 Jul 2025 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/cdn-to-origin-certificates/</guid><description>&lt;p&gt;There&amp;rsquo;s a common assumption that because a CDN handles the TLS connection your users see — the certificate shown in the browser&amp;rsquo;s address bar — you don&amp;rsquo;t need to think too hard about certificates on your origin. That&amp;rsquo;s wrong, and the consequences show up as cryptic error codes rather than obvious failures.&lt;/p&gt;
&lt;p&gt;A CDN like Akamai doesn&amp;rsquo;t act as a transparent tunnel. It terminates the TLS session from the client, inspects and processes the request, then opens a &lt;em&gt;new&lt;/em&gt; TLS session toward your origin. Two separate connections, two separate certificate validations.&lt;/p&gt;</description></item></channel></rss>