You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a nginx version with HTTP2 support is being used, that should be pretty easy. Do note that HTTP2 uses UDP/443, so public facing firewalls may need to be opened. The docs do list some limits that may need to be tweaked after activation.
Note: we use nginx proxying so we might need to apply this on the proxy as well as on the static serving nginx.
Looks like there's no option to enable proxy upstream to use HTTP2. The recommended way seems to be to keepalive the upstream connections instead, which makes sense when you think about it.
Study also if we can activate it for small images (100px version of products images).
I don't know of any way to limit HTTP2 to specific paths. It would be enabled for all resources on the same host.
Nginx supports htpp 2.0 which can pipeline small requests.
This can speed up small images and assets loading significantly.
Study how to do that.
Note: we use nginx proxying so we might need to apply this on the proxy as well as on the static serving nginx.
Study also if we can activate it for small images (100px version of products images).
The text was updated successfully, but these errors were encountered: