<?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[Debanshu Panigrahi]]></title><description><![CDATA[Documenting my technical journey through code, comprehensive documentation, and personal opinions on the evolving tech landscape. From deep-dive tutorials to ho]]></description><link>https://blog.debanshupanigrahi.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/69cdf6922d4d5bd0f080b8d3/aafafe8c-6236-40e6-b83d-4b879b022fc9.png</url><title>Debanshu Panigrahi</title><link>https://blog.debanshupanigrahi.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sat, 23 May 2026 12:28:45 GMT</lastBuildDate><atom:link href="https://blog.debanshupanigrahi.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Quickserve with HTTPS: The No-Fuss Guide]]></title><description><![CDATA[If you're using the QuickServe extension in VS Code and need a Secure Context for local testing (Service Workers, Clipboard API, etc.), you don't need to manually wrestle with OpenSSL via the CLI anym]]></description><link>https://blog.debanshupanigrahi.dev/quickserve-with-https-the-no-fuss-guide</link><guid isPermaLink="true">https://blog.debanshupanigrahi.dev/quickserve-with-https-the-no-fuss-guide</guid><dc:creator><![CDATA[Debanshu Panigrahi]]></dc:creator><pubDate>Tue, 28 Apr 2026 15:28:45 GMT</pubDate><content:encoded><![CDATA[<p>If you're using the <a href="https://marketplace.visualstudio.com/items?itemName=debanshupanigrahi.quickserve">QuickServe</a> extension in VS Code and need a Secure Context for local testing (Service Workers, Clipboard API, etc.), you don't need to manually wrestle with OpenSSL via the CLI anymore.</p>
<p>QuickServe has a built-in <strong>Self-Healing Mode</strong> that handles certificate generation for you. You just need to tweak your <code>settings.json</code>.</p>
<p>Here is the exact setup.</p>
<h2>The Baseline Configuration</h2>
<p>Navigate to <strong>Settings &gt; Extensions &gt; User/Workspace &gt; QuickServe Configuration</strong> (or just open your <code>settings.json</code>).</p>
<p>You'll be targeting this JSON block:</p>
<pre><code class="language-json">"quickserve.https": {
    "enable": true,
    "certPath": "",
    "keyPath": ""
}
</code></pre>
<p>By setting <code>"enable": true</code> and leaving the paths empty, QuickServe takes over. What happens next depends on what is installed on your machine.</p>
<hr />
<h2>Method 1: The Self-Healing Fallback (With Browser Warning)</h2>
<p>If you don't have any local Certificate Authority tools installed, do absolutely nothing else.</p>
<p>With the empty paths above, QuickServe's Self-Healing Mode kicks in. It automatically generates a standard self-signed certificate in the background to serve your project over HTTPS.</p>
<p><strong>Result:</strong> Your browser will throw an <code>ERR_CERT_AUTHORITY_INVALID</code> warning because it's self-signed. Just click <strong>Advanced &gt; Proceed to localhost</strong> to bypass it, and you're good for quick testing.</p>
<hr />
<h2>Method 2: Trusted Local CA (No Browser Warning)</h2>
<p>Use <code>mkcert</code> to create a local Certificate Authority. This permanently prevents browser warnings and avoids strict cross-origin blocks.</p>
<h3>1. Install mkcert:</h3>
<pre><code class="language-shell"># macOS
brew install mkcert

# Windows (using Chocolatey)
choco install mkcert

# Linux (Ubuntu/Debian)
sudo apt install libnss3-tools mkcert
</code></pre>
<h3>2. Setup the local CA (Run once per machine):</h3>
<pre><code class="language-shell">mkcert -install
</code></pre>
<h3><strong>3. Let QuickServe Take Over:</strong></h3>
<p>With <code>mkcert</code> installed and the <code>certPath</code>/<code>keyPath</code> still empty in your <code>settings.json</code>, simply restart the QuickServe extension. The Self-Healing Mode will detect <code>mkcert</code> and automatically generate a fully trusted local certificate for you.</p>
<p><strong>Result:</strong> A smooth, trusted <a href="https://127.0.0.1"><code>https://127.0.0.1</code></a> connection. No red text, no warnings.</p>
<hr />
<h2>Bonus: The Manual Override</h2>
<p>If you already have your own custom OpenSSL certificates and want to bypass the Self-Healing Mode entirely, just provide the absolute paths in your <code>settings.json</code>:</p>
<p>JSON</p>
<pre><code class="language-json">"quickserve.https": {
    "enable": true,
    "certPath": "/absolute/path/to/cert.pem",
    "keyPath": "/absolute/path/to/key.pem"
}
</code></pre>
<p>Save the file, restart the extension, and QuickServe will use your specific files.</p>
]]></content:encoded></item></channel></rss>