Then, I review my whole nginx config, to check about all the HTTP2 settings.
AH SNAP MEANING UPDATE
I found pages about the NPN not being supported any more by Google, so I decided to update my nginx, by recompiling it against openssl 1.0.2 instead of the basic openssl 1.0.0 branch as it is from the various defaut packages this enabled the ALPN but did not solve my case. So, I decided to go through the web (GI MF). Then I debugged the HTTP2 using several tools as h2i or h2c. But as the page was in cache, no change resulted from this. As the late changes were about HTTP2, I decided to test the HTTP2. A review thanks to Qualys reported no issue and even granted an A score to the website (via the CDN and via the origin also). Then, I guessed : when I get the “Aw, Snap” page, the DevTools in Chrome report just nothing besides the SSL details. I decided to create two very simple HTML page with just a basic HTML link towards each other. I started debugging the code with no luck about this one. First asumption as it only occurs with a specific browser, it was a code issue : either HTML or, more probably, JS. The consequence of the bug was a almost random “Aw, Snap !” page : every time I clicked on an internal link or upon one load out of two. But, as there is always a but, it generated some random issues … with Google Chrome (and it’s opensource pendant, Chromium).
The performance restults are instantaneous. On a global purpose of optimisation of my website, I lately added some features and enhanced the HTTP2 delivery of the website.
0 kommentar(er)
