<?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>http/2 Archives - MIDAS - Room Booking System | Blog</title>
	<atom:link href="https://mid.as/blog/tag/http2/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>...Making your facilities work for you!</description>
	<lastBuildDate>Tue, 11 Feb 2025 14:07:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>Upgrading our servers to support HTTP/2</title>
		<link>https://mid.as/blog/upgrading-our-servers-to-support-http2/</link>
					<comments>https://mid.as/blog/upgrading-our-servers-to-support-http2/#respond</comments>
		
		<dc:creator><![CDATA[midas]]></dc:creator>
		<pubDate>Thu, 13 Jul 2017 14:32:33 +0000</pubDate>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Tech Insight]]></category>
		<category><![CDATA[http/2]]></category>
		<category><![CDATA[service status]]></category>
		<guid isPermaLink="false">https://mid.as/blog/?p=2111</guid>

					<description><![CDATA[<p>As part of our ongoing commitment to the services we provide to our &#8220;cloud hosted&#8221; customers, we&#8217;ll shortly be upgrading our client servers to support HTTP/2. HTTP/2 is the first major new version of the HyperText Transfer Protocol (HTTP) for two decades. It will eventually replace the previous HTTP/1.1 protocol which was standardized way back [&#8230;]</p>
<p>The post <a href="https://mid.as/blog/upgrading-our-servers-to-support-http2/">Upgrading our servers to support HTTP/2</a> appeared first on <a href="https://mid.as/blog">MIDAS - Room Booking System | Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[<figure class="wp-block-post-featured-image"><img fetchpriority="high" decoding="async" width="960" height="350" src="https://mid.as/blog/wp-content/uploads/2017/07/network-switch.jpg" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="Network Switch" style="object-fit:cover;" srcset="https://mid.as/blog/wp-content/uploads/2017/07/network-switch.jpg 960w, https://mid.as/blog/wp-content/uploads/2017/07/network-switch-300x109.jpg 300w, https://mid.as/blog/wp-content/uploads/2017/07/network-switch-768x280.jpg 768w" sizes="(max-width: 960px) 100vw, 960px" /></figure>


<p>As part of our ongoing commitment to the services we provide to our &#8220;cloud hosted&#8221; customers, we&#8217;ll shortly be upgrading our client servers to support HTTP/2.</p>



<p>HTTP/2 is the first major new version of the HyperText Transfer Protocol (HTTP) for two decades. It will eventually replace the previous HTTP/1.1 protocol which was standardized way back in 1997.</p>



<p>The primary goal of HTTP/2 is to overcome many of the shortcomings of the twenty-year old HTTP/1.1 protocol, particularly in relation to how content is delivered over the internet.</p>



<p>HTTP/2 focuses on optimizing the communication and flow of content between <a href="https://mid.as/glossary/web-server" class="dfn">web servers</a> and <a href="https://mid.as/glossary/web-browser" class="dfn">web browsers</a>. When a user connects to a web site, their browser negotiates an HTTP session with the server. The type of session created will vary depending on the features supported by the browser and the server. If both ends support the latest HTTP/2 protocol, the server uses the HTTP/2 protocol to shape and optimize traffic before it passes through the network back to the browser.</p>



<p>Once the browser and server agree to use HTTP/2, they can utilize additional features such as compression and multiplexing to optimize the connection. If either the web server or the user&#8217;s web browser doesn&#8217;t support HTTP/2, the connection will fall back to the HTTP/1.1 protocol.</p>



<h2 class="wp-block-heading">Benefits of HTTP/2</h2>



<p>One of the main improvements over HTTP/1.1 is that HTTP/2 uses simultaneous connections (or multiplexing). Previously only one resource can be fetched from the server at a time. However with HTTP/2 multiple resources can be fetched over a single connection concurrently.</p>



<p>Another benefit is header optimization. Every request over HTTP contains header information. With HTTP/1.1, many of these headers are repeated over a single session. HTTP/2 removes redundant headers while compressing the remaining headers, leading to performance improvements.</p>



<h2 class="wp-block-heading">Benefits to cloud-hosted MIDAS users</h2>



<p>In terms of MIDAS, the benefit of our client servers supporting HTTP/2 is that users will see notable improvements in page load speed and responsiveness when using MIDAS.</p>



<p>In our pre-testing, we saw page load times via HTTP/2 <strong style="color: lime;">improve by some 20%</strong> over the same pages loaded via HTTP/1.1</p>



<h2 class="wp-block-heading">When will the upgrade happen?</h2>



<p>We&#8217;ll be upgrading our client servers to support HTTP/2 over the coming weekend (15/16th July 2017). Other than a quick server restart, no additional downtime is expected. For more information, check our dedicated <a href="https://midas.network">Service Status</a> site (which already supports HTTP/2!), and follow us <a href="https://twitter.com/mid_as">on Twitter</a> for updates.</p>



<h2 class="wp-block-heading">Will I need to do anything?</h2>



<p>No action is required on your part!</p>



<p>If you&#8217;re running a modern operating system and web browser, you won&#8217;t need to do anything. Your browser will already support HTTP/2, and you&#8217;ll still access MIDAS in exactly the same way. Once our servers are HTTP/2 enabled over the weekend, your browser will adjust accordingly.</p>



<p>If you&#8217;re not running an HTTP/2 compliant browser/operating system don&#8217;t worry, you&#8217;ll still be able to connect to your hosted MIDAS system over HTTP/1.1 as before. For an improved MIDAS experience though, you may like to consider upgrading your operating system &amp; browser to one that supports HTTP/2.</p>



<ul class="wp-block-list">
<li><img decoding="async" style="width: 32px; height: 32px;" title="Edge" src="//mid.as/img/logos/me.png" alt="Edge"> <img decoding="async" style="width: 32px; height: 32px;" title="Chrome" src="//mid.as/img/logos/gc.png" alt="Chrome"> <img decoding="async" style="width: 32px; height: 32px;" title="Firefox" src="//mid.as/img/logos/ff.png" alt="Firefox"> Current versions of Edge, Chrome, and Firefox browsers fully support HTTP/2.</li>



<li><img decoding="async" style="width: 32px; height: 32px;" title="Safari" src="//mid.as/img/logos/sf.png" alt="Safari"> Current versions of Safari support HTTP/2 on OSX 10.11+</li>



<li><img decoding="async" style="width: 32px; height: 32px;" title="Internet Explorer" src="//mid.as/img/logos/ie.png" alt="Internet Explorer"> Internet Explorer 11+ supports HTTP/2 on Windows 10 only</li>
</ul>



<p><strong>UPDATE:</strong> Our network is now fully HTTP/2 enabled, and we&#8217;re seeing some great performance improvements too!</p>
<p>The post <a href="https://mid.as/blog/upgrading-our-servers-to-support-http2/">Upgrading our servers to support HTTP/2</a> appeared first on <a href="https://mid.as/blog">MIDAS - Room Booking System | Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://mid.as/blog/upgrading-our-servers-to-support-http2/feed/</wfw:commentRss>
			<slash:comments>0</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 
Lazy Loading (feed)
Database Caching 2/33 queries in 0.007 seconds using Disk

Served from: mid.as @ 2026-04-08 06:42:14 by W3 Total Cache
-->