I've just installed and enabled, and the first thing I get on a previously working dev site running Ngnix and https2 is 500 Bad Gateway. It's also possible you can see a 502 error.
It turns out that the problem is that the headers generated by PHP are too big when Push is enabled.
The exact solution depends on the configurations of your Nginx but most likely you will need to adjust your nginx.conf file to allow larger buffers. See https://stackoverflow.com/questions/23844761/upstream-sent-too-big-heade... for some discussion about what to change for various Nginx configurations.
A good starting point is:
fastcgi_buffers 16 16k;
fastcgi_buffer_size 32k;
You may need to experiment to get the correct sizes.
Comments
Comment #2
jeff veit commentedI suggest that this info goes into the documentation/README or on the project page.
Comment #3
wim leersAny chance you don't have CSS+JS aggregation enabled? Only then would this add lots of headers.
Comment #4
jeff veit commentedYeah Wim, I do: it's a dev environment at the moment.
Comment #5
wim leersI guess I could change this to only work when CSS+JS aggregation is enabled, then this problem wouldn't occur anymore.
We'd then also want a warning in the status report that no Server Push will happen because CSS+JS aggregation are not enabled.
Comment #6
prudloff commentedWe had the same issue in one of our dev environments.
The attached patch only adds assets to the Link header if JS or CSS preprocess is enabled.
Comment #7
prudloff commentedComment #8
wim leersThanks, @prudloff! :)
Rather than retrieving the relevant configuration by calling into a global singleton, we should inject the relevant configuration into the service.
Comment #9
wim leers#8.2: On second thought, a status report entry is probably overkill. It obviously is weird to send dozens upon dozens of "preload"
Linkheaders.That leaves only #8.1. Will take that on.
Comment #10
wim leersComment #11
wim leers🚢
Comment #13
wim leers