nginx支持http2協議

1.http2協議

• HTTP 2.0 的主要目標是改進傳輸性能，實現低延遲和高吞吐量。從另一方面看，HTTP 的高層協議語義並不會因為這次版本升級而受影響。所有HTTP 首部、值，以及它們的使用場景都不會變。
• 現有的任何網站和應用，無需做任何修改都可以在HTTP 2.0 上跑起來。不用為了利用HTTP 2.0 的好處而修改標記。HTTP 服務器必須運行HTTP 2.0 協議，但大部分用戶都不會因此而受到影響
• centos6安裝參考:
• https://imhanjm.com/2017/04/20/nginx%20http2%E7%BC%96%E8%AF%91%E5%AE%89%E8%A3%85/
• http://blog.csdn.net/littlesmallless/article/details/59173287

2.編譯安裝nginx

#1.安裝依賴
[root@hadoop_node1 ~]# yum install  -y  gcc  gcc-c++  pcre  pcre-devel  openssl-devel  zlib  zlib-devel
#2.下載安裝
[root@hadoop_node1 ~]# cd /usr/local/src/
[root@hadoop_node1 src]# wget http://nginx.org/download/nginx-1.10.3.tar.gz
[root@hadoop_node1 src]# tar xf nginx-1.10.3.tar.gz 
[root@hadoop_node1 src]# cd nginx-1.10.3/
#3.編譯參數
[root@hadoop_node1 nginx-1.10.3]# ./configure --user=nginx --group=nginx --prefix=/usr/local/nginx-1.10.3 --with-http_stub_status_module --with-http_ssl_module --with-http_v2_module
[root@hadoop_node1 nginx-1.10.3]# make && make install

 

• --with-http_v2_module 支持http2協議

[root@hadoop_master nginx]# /usr/local/nginx/sbin/nginx -V
nginx version: nginx/1.10.3
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-16) (GCC) 
built with OpenSSL 1.0.2k-fips  26 Jan 2017
TLS SNI support enabled
configure arguments: --user=nginx --group=nginx --prefix=/usr/local/nginx-1.10.3 --with-http_stub_status_module --with-http_ssl_module --with-http_v2_module

3.生成證書

• 因為沒有真的證書，所以生成一個偽證書

[root@hadoop_node1 nginx-1.10.3]# ln -s /usr/local/nginx-1.10.3/ /usr/local/nginx
[root@hadoop_node1 nginx-1.10.3]# cd /usr/local/nginx/conf/
[root@hadoop_node1 conf]# mkdir key
[root@hadoop_node1 conf]# cd key/
#自定義密碼
[root@hadoop_node1 key]# openssl genrsa -des3 -out server.key 1024
Generating RSA private key, 1024 bit long modulus
..........++++++
..........++++++
e is 65537 (0x10001)
Enter pass phrase for server.key:
Verifying - Enter pass phrase for server.key:
#簽發證書
[root@hadoop_node1 key]# openssl req -new -key server.key -out server.csr
Enter pass phrase for server.key:
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:CN
State or Province Name (full name) []:BJ
Locality Name (eg, city) [Default City]:BJ
Organization Name (eg, company) [Default Company Ltd]:SDU
Organizational Unit Name (eg, section) []:SA
Common Name (eg, your name or your server's hostname) []:xiaojin
Email Address []:[e-mail]

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:123456
An optional company name []:123456
[root@hadoop_node1 key]# cp server.key server.key.ori
[root@hadoop_node1 key]# openssl rsa -in server.key.ori -out server.key
Enter pass phrase for server.key.ori:
writing RSA key
[root@hadoop_node1 key]# openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
Signature ok
subject=/C=CN/ST=BJ/L=BJ/O=SDU/OU=SA/CN=xiaojin/emailAddress=[e-mail]
Getting Private key

4.修改nginx的配置文件

[root@hadoop_node1 conf]# cat nginx.conf
worker_processes  1;
events {
    worker_connections  1024;
}
http {
    include       mime.types;
    default_type  application/octet-stream;
    sendfile        on;
    keepalive_timeout  65;
    server {
        listen     80;
        server_name  10.0.0.71;
        if ($scheme ~ http) {
            return https://$server_name:8443$request_uri;
        }
        location / {
            root   html;
            index  index.html index.htm;
        }
        location = /50x.html {
            root   html;
        }
    }
    server {
        listen    8443 ssl http2 default_server; 
        server_name  10.0.0.71;
        ssl_certificate     key/server.crt;
        ssl_certificate_key key/server.key;
        location / {
            root   html;
            index  index.html index.htm;
        }
        location = /50x.html {
            root   html;
        }
    }
}

• 檢查防火牆是否開啟，是否開啟8443和80端口　　

[root@hadoop_node1 conf]# iptables -I INPUT -p tcp --dport 80 -j ACCEPT 
[root@hadoop_node1 conf]# iptables -I INPUT -p tcp --dport 8443 -j ACCEPT 
[root@hadoop_node1 conf]# /usr/local/nginx/sbin/nginx -t
nginx: the configuration file /usr/local/nginx-1.10.3/conf/nginx.conf syntax is ok
nginx: configuration file /usr/local/nginx-1.10.3/conf/nginx.conf test is successful
[root@hadoop_node1 conf]# /usr/local/nginx/sbin/nginx 
[root@hadoop_node1 conf]# ss -lntup|grep 8
tcp    LISTEN     0      128       *:80                    *:*                   users:(("nginx",pid=7582,fd=6),("nginx",pid=7581,fd=6))
tcp    LISTEN     0      128       *:22                    *:*                   users:(("sshd",pid=1885,fd=3))
tcp    LISTEN     0      128       *:8443                  *:*                   users:(("nginx",pid=7582,fd=7),("nginx",pid=7581,fd=7))
tcp    LISTEN     0      128      :::22                   :::*                   users:(("sshd",pid=1885,fd=4))

• 驗證方法
• 方法一

1. 使用Chrome訪問啟用http2的站點，比如Jackie的環境為https://10.0.0.71:8443。
2. 新開TAB頁，在地址欄中輸入chrome://net-internals/#http2，檢查HTTP/2 sessions下的表格。
3. 確認表格里是否出現了上一步訪問的主機地址，比如10.0.0.71:8443。

• 方法二

1. 使用curl命令，參考HTTP/2 with curl，執行如下命令，確認站點返回的協議是否為HTTP
2. curl --http2 -I 10.0.0.71:8443
3. 如執行上述命令時遇到如下錯誤，說明系統當前安裝的curl還不支持HTTP2協議。
4. curl https://10.0.0.71:8443/ --http2 curl: (1) Unsupported protocol
5. 可以執行如下命令，檢查系統當前安裝的curl支持的特性列表，確認是否包含HTTP2。
6. curl -V curl 7.47.0 (i686-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smb smbs smtp smtps telnet tftp Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP UnixSockets
7. 從前述輸出信息可以了解到，當前安裝的curl還不支持HTTP2。
8. 這時可參考如何啟用curl命令HTTP2支持重新編譯curl，加入HTTP2的支持。

• 方法三

1. 安裝Chrome插件HTTP/2 and SPDY indicator，安裝完畢后訪問啟用HTTP2的站點，如果地址欄出現藍色的閃電，說明站點已啟用HTTP2。

• Nginx跨域優化

add_header 'Access-Control-Allow-Origin' '*';
add_header 'Access-Control-Allow-Methods' 'POST,GET,OPTIONS';
add_header 'Access-Control-Allow-Headers' 'application/json,X-Requested-With,Content-Type,Accept';