<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Http-Client on CuraSec</title><link>https://curasec.metacog.co.kr/tags/http-client/</link><description>Recent content in Http-Client on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 Oct 2026 17:10:43 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/http-client/index.xml" rel="self" type="application/rss+xml"/><item><title>Go headerscrub: drops auth headers on cross-origin redirects</title><link>https://curasec.metacog.co.kr/insights/2026-10-06-kofiadeyemiq-headerscrub-69/</link><pubDate>Tue, 06 Oct 2026 17:10:43 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-06-kofiadeyemiq-headerscrub-69/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Go&amp;rsquo;s default http.Client forwards all caller-set headers (including API keys and auth tokens) through cross-origin redirects — this library demonstrates the risk pattern and a mitigation worth evaluating for any Go service making outbound HTTP calls with sensitive headers.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>