bring 3 simple steps HTTP / 2 performance to legacy Web applications

3:58 PM
bring 3 simple steps HTTP / 2 performance to legacy Web applications -

Introduction to HTTP / 2

In May 2015, the IETF ratified HTTP / 2 as the latest version of the HTTP protocol. This is the first extension to HTTP since HTTP 1.1 was in 1997

Screenshot of Microsoft Internet Explorer 3 runs under Windows 95 courtesy of Microsoft used published.

If you can remember 3 Netscape or Internet Explorer to use, you can see firsthand how websites and web applications developed in this period from simple text-based pages with a handful of small images to the media-rich, interactive experiences that we take for granted today.

In an effort to make the web experience better for users, Google developed the SPDY protocol. SPDY manipulated to make the interaction between compatible browsers and servers page load more efficiently, and also servers enabled content to push to the browser before it was requested.

HTTP / 2 is largely based on SPDY, defining these mechanisms like. a standard for compatibility across all browsers and Web servers

Why Upgrade to HTTP / 2

a word:. Power

HTTP / 2 is backward compatible with older versions of HTTP, but a HTTP / 2 server provides users of HTTP / 2 browser more responsive user experience. HTTP / 2 accelerated load times by:

  • HTTP header compression
  • loading page elements in parallel over a single TCP connection,
  • Pushing content from the server (instead of single "GET" requests of waiting,
  • avoiding head-of-line blocking

As HTTP / 2 upgrade?

the Hard Way

The latest version of IIS (Windows 10 / Server 2016) comes with HTTP / 2 support, and other popular web servers (eg Apache, nginx) plan their HTTP / 2 versions in 2015 later posting. switched HTTP / 2 is now on each of your Windows Server server operating system replaces the latest version of IIS version, or to run in the case of Apache, to allow the source code patching the HTTP / 2 module.

the easy way

If the effort, cost and risk of the entire web server farm to the latest version to update relegated HTTP / 2 in the "too hard basket" NetScaler offers simple low-risk alternative.

  1. Upgrade your NetScaler to 11.0 (or higher)
  2. Check if your NetScaler has an Enterprise or Platinum license
  3. Turn HTTP / 2 on the NetScaler (Easy Step-By-Step instructions here)

How NetScaler HTTP / 2 to legacy applications bring & Server?

At power HTTP / 2 on the NetScaler compatible browsers will enjoy the improved performance of the new protocol. Use On the server side, the proxies NetScaler browser sessions on the server HTTP / 1.x, so there are no changes to the server is necessary.

Just One Caveat

HTTP / 2 contains the security within the HTTP protocol, in which security was an add-on outside the HTTP session beforehand. Although the HTTP / 2 standard security mandate, only some browsers encrypted HTTP support / 2, it is to make a de facto requirement. HTTP / 2 therefore requires SSL hardware for maximum performance and is only on the MDX and SDX platforms.

As HTTP / 2 to bring performance to non-compatible browsers

The latest versions of Chrome, Safari and Firefox support HTTP / 2, but users of older versions or other browsers like Internet Explorer are not so lucky. To ensure the fastest possible browser experience for these users, you need NetScaler HTTP optimization to enable features. NetScaler HTTP Optimization improves the efficiency of interaction between the browser and the server technologies such as HTTP compression, use content caching, and streamlining providing content such as style sheets and Javascript.

Previous
Next Post »
0 Komentar