Nginx nginx 1.13.9 - released

Interested to know if anyone tried - GitHub - horzadome/nginx_preloadheaders: nginx lua module for automatically determining resources which should be preloaded and for http2 server push

---

 

Have spent a few minutes on server push and fastcgi cached pages.

HTTP/2 server push could or better should be a lot easier to setup.
For example one single txt setup. uri ... push assets ....

The current Server push Nginx setup opportunities are nice for a single CV website page but nothing more.

As it won't work that simple for simple dynamic content with static assets.
Where the assets are always the same (but page per page different).
Only the text could change over time. In short, it should not be so difficult.

To add a simple header to a Wordpress cached page.
You now have to use a lot of extra nonsense. And that for only 1 header.

For example fastcgi cached Wordpress test page.

Code:

location /about {
add_header Link "</style.css>; as=style; rel=preload;";
}

Of course won't work as it can't find the source. Error 404.

Code:

location /about {
try_files $uri $uri/ /index.php?$args;
add_header Link "</style.css>; as=style; rel=preload;";
}

Seems to work fine at first sight.
But there is one problem.
And that is that it doesn't add the header.

Code:

location /about {
  add_header Link "</style.css>; as=style; rel=preload;";
  include fastcgi_params;
  fastcgi_pass php;
  fastcgi_cache_bypass $skip_cache;
  fastcgi_no_cache $skip_cache;
  fastcgi_cache WORDPRESS;
}

Works fine as long as it is cached.
If the cache is expired bye bye page as it can't be cached again.
Adding try_files $uri $uri/ /index.php?$args; result in the same problem as written above. Page loaded correctly but no header.

Proxy pass and fastcgi pass results in bad gateway but that is due to the setup.
The easiest solution should if uri then.
Problem is that Nginx does not allow headers over there.

 

Won't work as if uri gets the same error.

I am not a Nginx specialist and I only looked at it for a few minutes.
But...what is more difficult than adding 1 header at 1 url. An thats it.

Code:

url /about
add_header Link "</style.css>; as=style; rel=preload;";
url /contact
add_header Link "</style2.css>; as=style; rel=preload;";
etc etc.

You need to keep simple things simple.
Just like Fastly's Varnish.

Code:

if (fastly_info.is_h2 && req.url ~ "^/contact")
  {
    h2.push("/assets/jquery.js");
}

 

Won't work as can be seen at Nginx - nginx 1.13.9 - released first example.

 

Problem is simple yet annoying due to the limitations of Nginx.
As Nginx is aggressive, it takes the / location too literally.

Result it will break the CMS dynamic content as the CMS itself is directing the / location to its destination. The / location does not actually exist in a CMS other than /root or /.

It is an index redirect i.e. /index.php?$args.
And at that point, it goes wrong because both frustrate each other at all the locations other than root.

For example location /contact
Nginx can't find the content (error 404).
And that is true because there is no /contact. It is /index.php?$args with the virtual location /contact.
On his turn: The CMS can't redirect because the location is hard copied in Nginx.

Nginx won't allow headers with if.
With if uri add header problem would be solved in seconds.

 

Thanks . True. My mistake. But already tested.
Problem is not the specific 'LINK assigning a mapped variable' it's the hard coded /location in combination with dynamic links. What causes the problem.

 

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.

 

There will certainly be a solution.
Wonder if it is my solution.

It takes more time than a few minutes.
For very little benefit.

In addition, all examples from respective company's as Fastly, Nginx and Cloudflare are with static content only.

With a recommendation not to use it with cached content, which fastcgi cache in fact is.

 

Nup I don't use plug-ins on the Wordpress test site.

Tried GitHub - horzadome/nginx_preloadheaders: nginx lua module for automatically determining resources which should be preloaded and for http2 server push
It's great. To great. It pushes way to aggressively.
For example visiting the second page after the first.

It will push all the assets, including images and fonts from page 1 to page 2, 3, 4 etc. Too bad there is no commitment to the project since Aug 25, 2016 anymore.

Second it is running on Lua and Nginx.

Lua Nginx has a problematic history with OpenSSL.
Given the fact that a new OpenSSL around the corner with TLS 1.3.
TLS 1.3 has my preference.

 

About benefit and in particular server push on mobiles.

As @eva2000 rightly pointed out. "benefits are seen more on slower mobile device connections". Biggest problem is the quality of the network performance. And that is with the current mobile technology. Quite changeable in some areas and/or on
present-day phones:

Conclusion:

Source: http://papers.www2017.com.au.s3-website-ap-southeast-2.amazonaws.com/proceedings/p459.pdf

 

True.
But the most important thing that matters to me.
Even in the most ideal conditions, server push gives only minimal improvement.

There are so many different types of devices and browsers that the ideal mix and settings for server push client go or no go is very difficult.

What about your test results @eva2000 ? Both real life and via test pages as webpagetest.

It takes far too much time, for too little improvement. As I speak for myself.
Never Say Never Again. It will certainly be fine in the feature. It is only too early.