<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bash on NV Trends</title><link>https://blogs.nvtrends.com/tags/bash/</link><description>Recent content in Bash on NV Trends</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 17 Jun 2026 07:01:29 +0000</lastBuildDate><atom:link href="https://blogs.nvtrends.com/tags/bash/index.xml" rel="self" type="application/rss+xml"/><item><title>Make HTTP Requests Without Curl: Bash /dev/tcp Guide</title><link>https://blogs.nvtrends.com/posts/2026/http-requests-without-curl-bash-dev-tcp/</link><pubDate>Wed, 17 Jun 2026 07:01:29 +0000</pubDate><guid>https://blogs.nvtrends.com/posts/2026/http-requests-without-curl-bash-dev-tcp/</guid><description>&lt;p&gt;Imagine you are logged into a remote server, perhaps a highly stripped-down production environment or a minimal Docker container. You need to verify if an internal API is responding or if a specific port is open, but you quickly realize that the usual suspects—&lt;strong&gt;curl&lt;/strong&gt;, &lt;strong&gt;wget&lt;/strong&gt;, and even &lt;strong&gt;telnet&lt;/strong&gt;—are missing. In the world of modern DevOps and system administration, we often take these tools for granted. However, there is a powerful, &amp;ldquo;hidden&amp;rdquo; feature built directly into the Bash shell that allows you to communicate over the network using nothing but standard shell commands.&lt;/p&gt;</description></item></channel></rss>