Nginx nginx 1.13.9 - released

Jon Snow · Feb 23, 2018

Andy said: ↑

With every going on, is it safe to update yet? I hardly see a new nginx update with 5 pages of posts and it scares me.
Click to expand...

I upgraded some hours after it was released and everything was fine for me.

buik · Feb 23, 2018

eva2000 said: ↑

And as you know 3G mobile can have RTT of 300+ ms, so you can imagine a budget of 1000-2000ms means saving 1RTT 300+ ms on HTTP/2 Server Push is a huge deal.
Click to expand...

Absolutely true.
Fact to the matter is.
Can you achieve it right now. An no no no not tomorrow, not yesterday. Tonight?

eva2000 · Feb 23, 2018

Achieve what the target or the 1RTT savings with HTTP/2 push. The latter can be done now but the former is a work in progress usually I am around 2000-2600ms on 3G mobile tests for Speedindex for US East to US West distance tests before HTTP/2 Push for my forums which use adsense, piwik + google analytics. So you can see why I am excited for a 1RTT savings

buik · Feb 23, 2018

eva2000 said: ↑

Achieve what the target or the 1RTT savings with HTTP/2 push. The latter can be done now but the former is a work in progress usually I am around 2000-2600ms on 3G mobile tests for Speedindex for US East to US West distance tests before HTTP/2 Push for my forums which use adsense, piwik + google analytics. So you can see why I am excited for a 1RTT savings
Click to expand...

Please keep me informed about you progress.
I will continue to use server push on test systems but think that TLS 1.3 is running in production earlier.

eva2000 · Feb 23, 2018

Will do.. though next up on my wishlist is 103 Early Hints

HTTP Status Code 103: Early Hints

The 103 (Early Hints) informational status code indicates to the
client that the server is likely to send a final response with the
header fields included in the informational response.

Typically, a server will include the header fields sent in a 103
(Early Hints) response in the final response as well. However, there
might be cases when this is not desirable, such as when the server
learns that the header fields in the 103 (Early Hints) response are
not correct before the final response is sent.

A client can speculatively evaluate the header fields included in a
103 (Early Hints) response while waiting for the final response. For
example, a client might recognize a Link header field value
containing the relation type "preload" and start fetching the target
resource. However, these header fields only provide hints to the
client; they do not replace the header fields on the final response.

Aside from performance optimizations, such evaluation of the 103
(Early Hints) response's header fields MUST NOT affect how the final
response is processed. A client MUST NOT interpret the 103 (Early
Hints) response header fields as if they applied to the informational
response itself (e.g., as metadata about the 103 (Early Hints)
response).

A server MAY use a 103 (Early Hints) response to indicate only some
of the header fields that are expected to be found in the final
response. A client SHOULD NOT interpret the nonexistence of a header
field in a 103 (Early Hints) response as a speculation that the
header field is unlikely to be part of the final response.
Click to expand...

buik · Feb 23, 2018

eva2000 said: ↑

Will do.. though next up on my wishlist is 103 Early Hints
Click to expand...

Going for a long time, I fear.

Category: Experimental
Click to expand...

But now we are busy. Now mine.
Wish-list:
DANE
TLS 1.3
Nginx server push like netlify.com:

you’ll have to add rules like these to your project’s _headers file:

/server-push-path
Link: </js/example-script.js>; rel=preload; as=script
Link: </css/example-style.css>; rel=preload; as=style
Click to expand...

I do not ask that much. Most of it, is already a standard.

buik · Feb 25, 2018

eva2000 said: ↑

You can test this using webpagetest.org advanced options which can simulate packet loss as well
Click to expand...

Always test these scenarios also in real life. Example > Security - Changes coming to TLS (TLS v1.3)

eva2000 · Feb 25, 2018

bassie said: ↑

Always test these scenarios also in real life. Example > Security - Changes coming to TLS (TLS v1.3)
Click to expand...

yup indeed !

knguyen2015 · Feb 25, 2018

eva2000 said: ↑

Yup Cloudflare HTTP/2 HPACK full encoding patching worked on Nginx 1.13.9 master branch code tested below. The master branch code hasn't changed from official Nginx 1.13.9 release, so should work fine as well. Just compiling GCC 8.0.1 Feb 18th build right now and will retest with Nginx 1.13.9 official release + GCC 8.0.1 soon

Code (Text):

patching nginx http/2 full HPACK encoding support
nginx-1.13.9_http2-hpack.patch
patch -p1 < /usr/local/src/centminmod/patches/cloudflare/nginx-1.13.9_http2-hpack.patch
patching file auto/modules
Hunk #1 succeeded at 437 (offset 1 line).
patching file auto/options
patching file src/core/ngx_murmurhash.c
patching file src/core/ngx_murmurhash.h
patching file src/http/v2/ngx_http_v2.c
Hunk #1 succeeded at 274 with fuzz 1 (offset 27 lines).
Hunk #2 succeeded at 2076 with fuzz 1 (offset 54 lines).
patching file src/http/v2/ngx_http_v2.h
Hunk #6 succeeded at 414 (offset -1 lines).
patching file src/http/v2/ngx_http_v2_filter_module.c
Hunk #1 succeeded at 26 (offset 1 line).
Hunk #2 succeeded at 88 with fuzz 2 (offset 40 lines).
Hunk #3 succeeded at 187 with fuzz 2 (offset 45 lines).
Hunk #4 succeeded at 465 (offset 56 lines).
Hunk #5 succeeded at 473 (offset 56 lines).
Hunk #6 succeeded at 493 (offset 56 lines).
Hunk #7 succeeded at 540 (offset 56 lines).
Hunk #8 succeeded at 592 (offset 56 lines).
Hunk #9 succeeded at 1025 (offset 347 lines).
Hunk #10 succeeded at 1051 (offset 347 lines).
patching file src/http/v2/ngx_http_v2_table.c

nginx 1.13.9 from master compiles fine

h2load testing HTTP/2 HPACK Full Encoding also works ~93% HTTP/2 header space savings after 20 runs

Code (Text):

url=https://http2.domain.com

for i in $(seq 1 20); do echo "h2load run $i"; h2load $url -n $i | tail -6 | head -1; done

h2load run 1
traffic: 6.20KB (6350) total, 250B (250) headers (space savings 38.12%), 5.89KB (6033) data
h2load run 2
traffic: 12.12KB (12415) total, 264B (264) headers (space savings 67.33%), 11.78KB (12066) data
h2load run 3
traffic: 18.05KB (18480) total, 278B (278) headers (space savings 77.06%), 17.67KB (18099) data
h2load run 4
traffic: 23.97KB (24545) total, 292B (292) headers (space savings 81.93%), 23.57KB (24132) data
h2load run 5
traffic: 29.89KB (30610) total, 306B (306) headers (space savings 84.85%), 29.46KB (30165) data
h2load run 6
traffic: 35.82KB (36675) total, 320B (320) headers (space savings 86.80%), 35.35KB (36198) data
h2load run 7
traffic: 41.74KB (42740) total, 334B (334) headers (space savings 88.19%), 41.24KB (42231) data
h2load run 8
traffic: 47.66KB (48805) total, 348B (348) headers (space savings 89.23%), 47.13KB (48264) data
h2load run 9
traffic: 53.58KB (54870) total, 362B (362) headers (space savings 90.04%), 53.02KB (54297) data
h2load run 10
traffic: 59.51KB (60935) total, 376B (376) headers (space savings 90.69%), 58.92KB (60330) data
h2load run 11
traffic: 65.43KB (67000) total, 390B (390) headers (space savings 91.22%), 64.81KB (66363) data
h2load run 12
traffic: 71.35KB (73065) total, 404B (404) headers (space savings 91.67%), 70.70KB (72396) data
h2load run 13
traffic: 77.28KB (79130) total, 418B (418) headers (space savings 92.04%), 76.59KB (78429) data
h2load run 14
traffic: 83.20KB (85195) total, 432B (432) headers (space savings 92.36%), 82.48KB (84462) data
h2load run 15
traffic: 89.12KB (91260) total, 446B (446) headers (space savings 92.64%), 88.37KB (90495) data
h2load run 16
traffic: 95.04KB (97325) total, 460B (460) headers (space savings 92.88%), 94.27KB (96528) data
h2load run 17
traffic: 100.97KB (103390) total, 474B (474) headers (space savings 93.10%), 100.16KB (102561) data
h2load run 18
traffic: 106.89KB (109455) total, 488B (488) headers (space savings 93.29%), 106.05KB (108594) data
h2load run 19
traffic: 112.81KB (115520) total, 502B (502) headers (space savings 93.46%), 111.94KB (114627) data
h2load run 20
traffic: 118.74KB (121585) total, 516B (516) headers (space savings 93.61%), 117.83KB (120660) data

Click to expand...

Where can I download that patch on github?

eva2000 · Feb 26, 2018

knguyen2015 said: ↑

Where can I download that patch on github?
Click to expand...

On official centmin mod github repo's 123.09beta01 branch at centminmod/nginx-1.13.9_http2-hpack.patch at 123.09beta01 · centminmod/centminmod · GitHub

Log in / Register

Forums

Learn about Centmin Mod LEMP Stack today

Nginx nginx 1.13.9 - released

Jon Snow Active Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

knguyen2015 New Member

eva2000 Administrator Staff Member

.

Log in / Register

Useful Searches

Learn about Centmin Mod LEMP Stack today

Nginx nginx 1.13.9 - released

Jon Snow Active Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

buik “The best traveler is one without a camera.”

buik “The best traveler is one without a camera.”

eva2000 Administrator Staff Member

knguyen2015 New Member

eva2000 Administrator Staff Member

.