146

Fucking hell! HTTP2 is really cool!

I've never really used in in production before, just played around with it, but combined with the Phoenix framework, which is freaking fast on it's own, it's a pleasure to see all the assets just pop up instantly without any effort. And SSL/TLS is a must in order to use it, that's another plus.

Comments
  • 16
    Agreed! I-devices just can't handle it. Working at a hosting company, this is the only reason why we're not implementing it yet :(
  • 13
    @linuxxx Haha, FUCK I-devices ;)
  • 4
    @linuxxx what iPhone can't handle http2?? Or I understood wrong? I don't have an iDevice to check honestly :/

    Out of scope, I added http2 in nginx config for the website anything else to add? (@AlexDeLarge)
  • 2
    @gitpush As far as I'm away, indeed
  • 12
    @AlexDeLarge Also, may I say that I'm happy you're still around? Yes, yes I may.
  • 7
    @gitpush Not much. The default port should be 443 when you use Nginx as the main entry point/proxy, because HTTP2 won't work without SSL/TLS. You should also double check the cipher set you're using, some aren't usable with HTTP2 anymore, because they're not secure (like, *gag* md5, of course and thus are blacklisted: https://http2.github.io/http2-spec/... )
  • 5
  • 2
    @AlexDeLarge gotta go double check thanks man
  • 2
    Aye, I agree, I am exploring http2, and it is so amazing, multiplexing and server push with default https!
  • 1
    @jAsE I hear Edge is the fastest (and safest) way to download anything these days! ;-)
  • 2
    My main Webserver Builds:
    - Apache2 version 2.4.25
    - SSL Let's Encrypt Cert on every Site
    - Apache2 Event_MPM as worker
    - Http/2
    - Tons of variables for fine tuning
    - PHP FPM 7.1
    - PHP aCPU and Redis Cache

    My Site Load Times are around 0.5 Seconds for 2 MB Data and Server response of 33ms.

    Im using a Root Server with Intel i7-6700K and 32 GB DDR4 RAM.
    This is legit tech porn for me

    Apache2 + Http/2 + PHP-FPM + PHP 7.1 = ❤❤❤❤
  • 1
  • 1
    @gitpull the only problem with nginx that I have found is that only the latest unstable version supports automatic server pushes via the link header which means building nginx yourself, of course if you want to use TLSv1.3 you have to do that anyways since it requires openssl 1.1.1 which the built in nginx packages are not built against.
  • 1
    @gitlab I am too stupid to understand your words. Could you rephrase them for me :)
  • 1
    @gitpull The latest version of TLS (v1.3) requires openssl 1.1.1 to be installed. Which you can easily download and install that requirement. However if nginx is built on a different openssl version (which if it comes from a distro it is) then you'll also need to download the nginx sources and build that.
  • 1
    @gitlab tbh I never set up TLS for my nginx env.
    I know I am doing really bad by that, but I just don't need it since no sensitive information is being sent.
  • 2
    @gitpull -_- letsencrypt makes this so easy it's unbelievable. You litterally download certbot do ./certbot --nginx and you follow the on screen prompts..... Shame on you
  • 1
  • 1
    Aww
    That's really sweet
  • 0
    @gitlab if you use ports on freebsd to install nginx, then it's fine...
    The server push thingy will be in stable pretty soon, i bet.
  • 0
    https://nginx.com/blog/...

    Testing this was huge fun
  • 0
    @devnope I am not a freebsd user though XD
  • 0
    cloudflare ftw
  • 0
    Maybe unrelated, but DigiCert (formerly Symantec/Norton) or LetsEncrypt...which is the better cert that people should use and trust more?
  • 0
    @stackodev norton/Symantec is a failed system imo.
    Let's encrypt is maybe not the CA we want, but the one we need these days.
Add Comment