{"id":40388,"date":"2024-02-28T12:58:29","date_gmt":"2024-02-28T10:58:29","guid":{"rendered":"https:\/\/hostkoss.com\/b\/?p=40388"},"modified":"2024-08-05T13:11:21","modified_gmt":"2024-08-05T10:11:21","slug":"http-2-nginx-ubuntu","status":"publish","type":"post","link":"https:\/\/hostkoss.com\/b\/tr\/http-2-nginx-ubuntu\/","title":{"rendered":"Ubuntu 18.04 \u00fczerinde Nginx’te HTTP\/2 deste\u011fini yap\u0131land\u0131rma"},"content":{"rendered":"\n

Nginx <\/strong>, verimli performans\u0131, d\u00fc\u015f\u00fck bellek t\u00fcketimi ve \u00e7e\u015fitli protokoller i\u00e7in g\u00fc\u00e7l\u00fc deste\u011fi nedeniyle bir\u00e7ok y\u00f6neticinin ve geli\u015ftiricinin kalbini kazanan a\u00e7\u0131k kaynakl\u0131 bir web sunucusudur. Bug\u00fcn, Nginx’te HTTP\/2 deste\u011finin yap\u0131land\u0131r\u0131lmas\u0131 hakk\u0131nda konu\u015faca\u011f\u0131z.<\/p>\n\n\n\n

HTTP\/2<\/strong>, sunucu ile kullan\u0131c\u0131 aras\u0131ndaki veri aktar\u0131m\u0131n\u0131 iyile\u015ftiren HTTP protokol\u00fcn\u00fcn bir evrimidir. E\u015fzamanl\u0131 ba\u011flant\u0131 say\u0131s\u0131nda bir s\u0131n\u0131ra sahip olan ve bu nedenle a\u011f\u0131r sayfalar\u0131n y\u00fcklenmesini yava\u015flatan HTTP 1.1’in yerini al\u0131r. HTTP\/2 bu sorunu paralel veri y\u00fcklemesine ve HTTP ba\u015fl\u0131k s\u0131k\u0131\u015ft\u0131rmas\u0131na izin vererek \u00e7\u00f6zer.<\/p>\n\n\n\n

HTTP\/2’ye ge\u00e7i\u015f neden \u00f6nemlidir?<\/h2>\n\n\n\n

HTTP\/2<\/strong> ‘ye ge\u00e7mek yaln\u0131zca<\/strong> web sitenizin y\u00fcklenmesini h\u0131zland\u0131rmakla kalmaz<\/strong>, ayn\u0131 zamanda veri aktar\u0131m\u0131n\u0131n g\u00fcvenli\u011fini de art\u0131r\u0131r. T\u00fcm modern taray\u0131c\u0131lar, HTTP\/2’yi desteklemek i\u00e7in web sitelerinin HTTPS kullanmas\u0131n\u0131 gerektirir, bu da sunucu ile ziyaret\u00e7iler aras\u0131ndaki veri iletimini daha g\u00fcvenli hale getirir.<\/p>\n\n\n\n

HTTP\/2’ye ge\u00e7i\u015f s\u00fcreci<\/h2>\n\n\n\n

HTTP\/2’yi kurmaya ba\u015flamadan \u00f6nce <\/strong>, Ubuntu 18.04 \u00e7al\u0131\u015ft\u0131ran ve Nginx y\u00fckl\u00fc bir sunucunuz olmal\u0131d\u0131r. Ayr\u0131ca, alan ad\u0131n\u0131z sunucuya y\u00f6nlendirilmeli ve bu alan ad\u0131 i\u00e7in bir SSL sertifikas\u0131 (\u00f6rne\u011fin, Let’s Encrypt) y\u00fckl\u00fc olmal\u0131d\u0131r.<\/p>\n\n\n\n

1. Sunucu kurulumu<\/h2>\n\n\n\n

Etki alan\u0131n\u0131z\u0131n yap\u0131land\u0131rma dosyas\u0131n\u0131 a\u00e7\u0131n:<\/p>\n\n\n\n

vim \/etc\/nginx\/sites-available\/your_domain<\/code><\/pre>\n\n\n\n
IPv6 ve IPv4 ba\u011flant\u0131lar\u0131 i\u00e7in HTTP\/2 deste\u011fi ekleyin:<\/p>\n\n\n\n
listen [::]:443 ssl hp2 ipv6only=on;\ndinle 443 ssl http2;<\/code><\/pre>\n\n\n\n
De\u011fi\u015fikliklerinizi kaydedin ve s\u00f6zdizimini kontrol edin:<\/p>\n\n\n\n
nginx -t<\/code><\/pre>\n\n\n\n
2. Geli\u015ftirilmi\u015f g\u00fcvenlik<\/h2>\n\n\n\n
G\u00fcvenli\u011fi art\u0131rmak i\u00e7in<\/strong> g\u00fcvenli olmayan \u015fifreleri hari\u00e7 tutun. Etki alan\u0131n\u0131z\u0131n yap\u0131land\u0131rma dosyas\u0131nda ssl_ciphers se\u00e7ene\u011fini de\u011fi\u015ftirin:<\/p>\n\n\n\n
ssl_ciphers EECDH+CHACHA20:EECDH+AES128:RSA+AES128:EECDH+AES256:RSA+AES256:EECDH+3DES:RSA+3DES:!MD5;<\/code><\/pre>\n\n\n\n
S\u00f6zdizimini kontrol edin ve sunucuyu yeniden ba\u015flat\u0131n:<\/p>\n\n\n\n
nginx -t\nsystemctl restart nginx.service<\/code><\/pre>\n\n\n\n
3. HTTP S\u0131k\u0131 Aktar\u0131m G\u00fcvenli\u011fi (HSTS) Ekleme<\/h2>\n\n\n\n
Daha da fazla g\u00fcvenlik i\u00e7in<\/strong>, Nginx yap\u0131land\u0131rma dosyan\u0131za HTTP Strict Transport Security ba\u015fl\u0131\u011f\u0131n\u0131 ekleyin. Bu ba\u015fl\u0131k, taray\u0131c\u0131lar\u0131n yaln\u0131zca HTTPS ba\u011flant\u0131lar\u0131n\u0131 kullanmas\u0131n\u0131 sa\u011flar.<\/p>\n\n\n\n
Nginx yap\u0131land\u0131rma dosyas\u0131nda:<\/p>\n\n\n\n
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains" always;<\/code><\/pre>\n\n\n\n
S\u00f6zdizimini kontrol<\/strong> edin ve sunucuyu yeniden ba\u015flat\u0131n.<\/p>\n\n\n\n
4. HTTP\/2’nin do\u011fru \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 kontrol etme.<\/h2>\n\n\n\n
HTTP\/2’yi curl komutunu kullanarak test edebilirsiniz:<\/p>\n\n\n\n
curl -I -L https:\/\/\u0432\u0430\u0448_\u0434\u043e\u043c\u0435\u043d<\/code><\/pre>\n\n\n\n
Sunucu yan\u0131t\u0131 HTTP\/2’den bahsetmelidir.<\/strong><\/p>\n\n\n\n
HTTP\/2 deste\u011fini kontrol etmek i\u00e7in Google Chrome ve geli\u015ftirici ara\u00e7lar\u0131n\u0131 da kullanabilirsiniz.<\/p>\n\n\n\n
Art\u0131k web siteniz HT<\/strong> TP protokol\u00fcn\u00fcn daha h\u0131zl\u0131 ve daha g\u00fcvenli bir s\u00fcr\u00fcm\u00fc olan HTTP\/2 ile \u00e7al\u0131\u015fmaya haz\u0131r<\/strong> \ud83d\ude80.<\/p>\n\n\n\n
\n
Sunucunuzu her zaman<\/strong> g\u00fcncel ve g\u00fcvenli tutmay\u0131 unutmay\u0131n. \u0130yi \u015fanslar!!!!<\/p>\n<\/blockquote>\n\n\n\n
<\/p>\n\n\n\n
Ayr\u0131ca okuyun:<\/strong><\/p>\n\n\n\n