Home PC Games Linux Windows Database Network Programming Server Mobile  
           
  Home \ Server \ NGINX Plus now fully supports HTTP / 2     - Using FTPClient to upload and download files in Java (Programming)

- Linux firewall security (Linux)

- How to download GOG games in Linux command line (Linux)

- Setting Linux desktop environment, achieve HiDPI display support (Linux)

- CentOS installation of the ftp (Linux)

- To learn linux security (Linux)

- LAMP and LNMP automated installation scripts (Server)

- PHP Performance Analysis and Experiment: Performance Micro Analysis (Programming)

- GAMIT baseline solution using batch were counted (Linux)

- Ubuntu ADSL dial-up Internet access (Linux)

- MongoDB simple replication configuration (Database)

- KVM QEMU virtual machine installation configuration under CentOS (Linux)

- Use Visual Studio to compile and use WinGDB remote debugging embedded Linux programs (Programming)

- Linux user opens a number of adjustment processes (Linux)

- ORA-12547: TNS: lost contact error Solution (Database)

- A brief description of Java 8 new features introduced syntax (Programming)

- To_teach you three strategies to prevent the LAN IP address theft (Linux)

- MySQL to manage multiple instances of method (Database)

- Oracle local user login authentication fails ORA-01031 insufficient privileges (Database)

- Linux script to copy the folder to all folders with the same name (Linux)

 
         
  NGINX Plus now fully supports HTTP / 2
     
  Add Date : 2018-11-21      
         
         
         
  Earlier, we announced support for HTTP / 2 protocol NGINX Plus R7. As the latest standard HTTP protocol designed HTTP / 2 is now a web application brings higher performance and security. (LCTT Annotation: the open source version of NGINX 1.95 also supports HTTP / 2 up.)

NGINX Plus implemented HTTP / 2 protocol can be seamlessly with existing Web sites and applications. Only you need a little change, regardless of the user choose what kind of browser, NGINX Plus can provide users with HTTP / 1.x with the best experience HTTP / 2 at the same time.

To support HTTP / 2 only through an optional package nginx-plus-http2. nginx-plus and nginx-plus-extras package supports SPDY protocol currently recommended for production site, because it is supported by most browsers and the code is quite mature.

 

Why use HTTP / 2?

HTTP / 2 data transmission more efficient, your application more secure. HTTP / 2 compared to the HTTP / 1.x five to improve performance characteristics:

Fully Multiplexed - remain active in a (keepalive) connections, HTTP / 1.1 according to strict mandatory order to process the request. A request must start before the end of the next request. HTTP / 2 eliminates this requirement, allowing parallel and out of order to process the request.

Single, persistent connections - Because HTTP / 2 allow the request completely reusable, so you can download all the objects in parallel on the page through a single connection. In HTTP / 1.x, multiple parallel connections to download resources, resulting in low efficiency of using the underlying TCP protocol.

Binary coded - Header information is sent using a compact binary format, instead of plain text format, saving transmission bytes.

Header compression - Headers dedicated HPACK compression algorithm to compress, which further reduces the data transmitted over the network bytes.

SSL / TLS encryption - in HTTP / 2, the mandatory use of SSL / TLS. In the RFC and not mandatory, which allows plaintext HTTP / 2, but all current Web browsers implement HTTP / 2 support only encryption. SSL / TLS can make your site more secure, and the use of HTTP / 2 will enhance the performance, the performance penalty for encryption and decryption process is reduced.

To learn more about HTTP / 2:

Read our white paper, which covers everything you need to know about HTTP / 2 in.
Downloaded by Google's Ilya Grigorik prepared a special edition, high-performance web browser eBook (LCTT Annotation: Partial coverage of HTTP / 2 in).
 

NGINX Plus how to implement HTTP / 2

Our HTTP / 2 implementation is based on SPDY support, which has been widely deployed (using NGINX NGINX Plus or nearly 75% of all websites use SPDY). When using NGINX Plus Deployment HTTP / 2, almost does not change the configuration of your application. This section will discuss how to achieve NGINX Plus supports HTTP / 2 in.

A HTTP / 2 Gateway

NGINX Plus as a HTTP / 2 gateway. It supports the client HTTP / 2-side Web browser with HTTP / 2 communication, while the conversion use HTTP / 2 request to the backend server communicate HTTP / 1.x (or FastCGI, SCGI, uWSGI, etc. - depending on your protocol currently being used).

Backward Compatibility

Over a period of time, you need to support both HTTP / 2 and HTTP / 1.x. At this writing, more than 50% of users use the Web browser already supports HTTP / 2, but it also means that nearly 50% of people do not use.

To support HTTP / 1.x and HTTP / 2, NGINX Plus realized on Next TLS Protocol Negotiation (NPN) extension. When a Web browser connects to the server, it will send a list of protocols supported by the server. If the list of protocols supported by the browser includes h2 - that is HTTP / 2, NGINX Plus uses the HTTP / 2 is connected to the browser. If your browser does not support NPN or h2 in the list sent to support the agreement, NGINX Plus will continue to fall to the HTTP / 1.x.

 

Steering HTTP / 2

NGINX companies will help you as much as possible a seamless transition to the use of HTTP / 2. This section describes the changes by your application to enable HTTP / 2 support, where just a few of NGINX Plus configuration changes.

 

Prerequisites

Use nginx-plus-http2 package upgrades to NGINX Plus R7. Note There is no support for HTTP / 2 version of nginx-plus-extras package.

 

To redirect all traffic to SSL / TLS

If your application has not yet use SSL / TLS encryption, and now it is a good time to enable it. Encryption your application can protect you against attacks from spyware and other intermediaries. Some search engine ranking in search results even for encrypted site improved. The following configuration block normal HTTP redirect all requests to the encrypted version of the site.

server {
listen 80;
location / {
return301 https: // $ host $ request_uri;
}
}
 

Enable HTTP / 2

To enable support for HTTP / 2, simply add the parameter http2 listen to all the instructions, but also including SSL parameters because the browser does not support encrypted HTTP / 2 request.

server {
listen 443 ssl http2 default_server;
ssl_certificate server.crt;
ssl_certificate_key server.key;
...
}
If necessary, restart NGINX Plus, for example, by running nginx -s reload command. To verify HTTP / 2 is working properly, you can use the "HTTP / 2 and SPDY indicator" plug-in Google Chrome and Firefox to check.

 

Precautions

Before you install nginx-plus-http2 package, you must remove the profile after SPDY all listen instruction parameters (using http2 and ssl parameters to replace it in order to enable support for HTTP / 2 in). After using this package, if there is spdy parameters listen instruction, NGINX Plus will not start.

If you use a Web application firewall in NGINX Plus tip (WAF), make sure it can resolve HTTP / 2, or move it to the back of NGINX Plus.

This version does not support the HTTP / 2 RFC defined in the "Server Push" feature. NGINX Plus future versions may support it.

NGINX Plus R7 support SPDY and HTTP / 2 (LCTT Annotation: But you can only use one). In future releases, we will deprecate support for the SPDY. Google in early 2016 will be deprecated SPDY, and therefore support both protocols nor necessary.

If sslpreferserver_ciphers set to on or use defined in Appendix A: TLS when ssl_ciphers Suite Black List in the list, the browser will appear 1.2 Ciper handshake-errors can not work properly. For details, see section 9.2.2 of the HTTP / 2 RFC.
     
         
         
         
  More:      
 
- CentOS iptables firewall enabled (Linux)
- How to set IonCube Loaders in Ubuntu (Linux)
- Through eight skills to let you become a super Linux end-user (Linux)
- MongoDB polymerization being given (Database)
- Linux kernel TCP / IP parameters analysis and tuning (Linux)
- CentOS install Memcached (Server)
- GAMIT 10.50 installed in Ubuntu 12.04 system (Linux)
- Ubuntu prompt / lack of boot space solutions (Linux)
- C ++ casts New Standard Comments (Programming)
- Linux hard drive failure Case Studies (Linux)
- Linux user login and IP restrictions (Linux)
- Objective-C basic program structure (Programming)
- The istgt PSD on ported to Mac OS X (Linux)
- Python Django model within the class meta Detailed (Programming)
- Java implementation of stacks and queues (Programming)
- To install Ganglia (Linux)
- Based AutoYaST automated installation of SUSE practice (Linux)
- Use GNU / Linux broadcasting of television programs (Linux)
- Analysis of memory mapping process in Linux x86-64 mode (Linux)
- E: Sub-process / usr / bin / dpkg returned an error code (1) error solution (Linux)
     
           
     
  CopyRight 2002-2020 newfreesoft.com, All Rights Reserved.