<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Apache Archives - EckoThemes</title>
	<atom:link href="https://slate-wp.ecko.me/tag/apache/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Slate WordPress Theme</description>
	<lastBuildDate>Fri, 09 Jul 2021 08:01:15 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://slate-wp.ecko.me/wp-content/uploads/2018/05/ecko-icon-50x50.png</url>
	<title>Apache Archives - EckoThemes</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Faster Response Time with Reverse Proxy Cache</title>
		<link>https://slate-wp.ecko.me/improve-response-time-with-reverse-proxy-cache/</link>
					<comments>https://slate-wp.ecko.me/improve-response-time-with-reverse-proxy-cache/#comments</comments>
		
		<dc:creator><![CDATA[Mike Ross]]></dc:creator>
		<pubDate>Sat, 07 Nov 2020 05:36:55 +0000</pubDate>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Apache]]></category>
		<category><![CDATA[Cache]]></category>
		<category><![CDATA[Nginx]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[Web]]></category>
		<guid isPermaLink="false">http://kitewp.ecko.me/?p=311</guid>

					<description><![CDATA[<p>These resources are then returned to the client as though they originated from the server itself (or servers themselves). While a forward proxy acts as an intermediary for its (usually nearby) associated clients and returns to them resources accessible on the Internet, a reverse proxy acts as an intermediary for its (usually nearby) associated servers [&#8230;]</p>
<p>The post <a href="https://slate-wp.ecko.me/improve-response-time-with-reverse-proxy-cache/">Faster Response Time with Reverse Proxy Cache</a> appeared first on <a href="https://slate-wp.ecko.me">EckoThemes</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>These resources are then returned to the client as though they originated from the server itself (or servers themselves). While a forward proxy acts as an intermediary for its (usually nearby) associated clients and returns to them resources accessible on the Internet, a reverse proxy acts as an intermediary for its (usually nearby) associated servers and only returns resources provided by those associated servers.</p>



<h3 class="wp-block-heading">NGINX</h3>



<p>NGINX is a high performance, open source web application accelerator that helps over 37% of the world’s busiest websites deliver more content, faster, to its users.</p>



<p>Companies deploy NGINX to manage the complexities and pitfalls associated with HTTP and to make their web applications more responsive, scalable, fast and secure. NGINX is commonly installed between the network and the application to offload concurrency processing, URL switching, HTTP load balancing, SSL termination, caching, and security policies.</p>



<h3 class="wp-block-heading">APACHE</h3>



<p>The Apache HTTP Server Project is a collaborative software development effort aimed at creating a robust, commercial-grade, featureful, and freely-available source code implementation of an HTTP (Web) server. The project is jointly managed by a group of volunteers located around the world, using the Internet and the Web to communicate, plan, and develop the server and its related documentation. This project is part of the Apache Software Foundation. In addition, hundreds of users have contributed ideas, code, and documentation to the project. This file is intended to briefly describe the history of the Apache HTTP Server and recognize the many contributors.</p>



<h3 class="wp-block-heading">VARNISH</h3>



<p>Varnish is an HTTP accelerator designed for content-heavy dynamic web sites. In contrast to other web accelerators, such as Squid, which began life as a client-side cache, or Apache and nginx, which are primarily origin servers, Varnish was designed as an HTTP accelerator. Varnish is focused exclusively on HTTP, unlike other proxy servers that often support FTP, SMTP and other network protocols.</p>
<p>The post <a href="https://slate-wp.ecko.me/improve-response-time-with-reverse-proxy-cache/">Faster Response Time with Reverse Proxy Cache</a> appeared first on <a href="https://slate-wp.ecko.me">EckoThemes</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://slate-wp.ecko.me/improve-response-time-with-reverse-proxy-cache/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/?utm_source=w3tc&utm_medium=footer_comment&utm_campaign=free_plugin

Page Caching using Disk: Enhanced 

Served from: slate-wp.ecko.me @ 2026-06-19 14:37:01 by W3 Total Cache
-->