<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SLOP on CodeCoverage</title>
    <link>https://www.codecoverage.de/tags/slop/</link>
    <description>Recent content in SLOP on CodeCoverage</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 11 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.codecoverage.de/tags/slop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Solving Proxy Hell: Why I Built &#39;Redir&#39; – A Surgical Environment Wrapper</title>
      <link>https://www.codecoverage.de/posts/cpp/redir_proxy/</link>
      <pubDate>Sat, 11 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://www.codecoverage.de/posts/cpp/redir_proxy/</guid>
      <description>&lt;h1 id=&#34;the-problem-when-no_proxy-is-ignored&#34;&gt;The Problem: When &amp;rsquo;no_proxy&amp;rsquo; is Ignored&lt;/h1&gt;&#xA;&lt;p&gt;In a modern corporate environment, working behind a proxy is often a necessity. To access internal resources while still allowing VS Code to download updates, plugins, and connect to LLM providers, I rely heavily on environment variables like &lt;code&gt;https_proxy&lt;/code&gt; and &lt;code&gt;no_proxy&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;However, I ran into a frustrating roadblock: A specific VS Code plugin I needed for my daily work consistently &lt;strong&gt;ignored the &lt;code&gt;no_proxy&lt;/code&gt; variable&lt;/strong&gt; but strictly enforced &lt;code&gt;https_proxy&lt;/code&gt;. This caused internal connections to fail because the plugin tried to route them through the corporate proxy, which couldn&amp;rsquo;t see our internal network.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
