<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Web-Servers on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/web-servers/</link>
		<description>Recent content in Web-Servers on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Mon, 21 Sep 2026 23:06:00 +0300</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/web-servers/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>What Is a Reverse Proxy and How Does It Work?</title>
				<link>https://www.compilemymind.com/posts/what-is-a-reverse-proxy/</link>
				<pubDate>Mon, 21 Sep 2026 23:06:00 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/what-is-a-reverse-proxy/</guid>
				<description>&lt;p&gt;Your application works perfectly on port 8080. Then you try to put it on the public internet.&lt;/p&gt;&#xA;&lt;p&gt;Suddenly, the application needs a trusted TLS certificate. It should answer for &lt;code&gt;app.example.com&lt;/code&gt;, not an internal hostname. Static files ought to be cached, &lt;code&gt;/api/&lt;/code&gt; must reach one service, and &lt;code&gt;/admin/&lt;/code&gt; must never be exposed by accident. When the backend restarts, users should receive a controlled error rather than a hanging connection.&lt;/p&gt;&#xA;&lt;p&gt;You could teach every application process to solve every one of those problems. A reverse proxy gives the system another option: put one deliberate boundary in front of the applications.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
