HTTP/2 is not the future, it’s the present

Re:HTTP/2 is not the future, it’s the present by magicbuzz on Wednesday April 12, 2017 @07:35AM (#14096664)

To be clear, Server Push as described in the article is not actually provided by nginx yet and thus by the server config in the article. I have no doubt that the awesome nginx folks will implement in due time though.

[ Parent | on HN ]

Re:HTTP/2 is not the future, it’s the present by avichalp on Wednesday April 12, 2017 @07:46AM (#14096713)

Its implementation is already present in nginx plus since 2015. https://www.nginx.com/blog/http2-r7/ Not sure if they are going to provide server pushes in the community version soon.

[ Parent | on HN ]

Re:HTTP/2 is not the future, it’s the present by juliangoldsmith on Wednesday April 12, 2017 @09:58AM (#14097704)

From your link:

>The “Server Push” feature defined in the HTTP/2 RFC is not supported in this release. Future releases of NGINX Plus might include it.

[ Parent | on HN ]

Re:HTTP/2 is not the future, it’s the present by scardine on Wednesday April 12, 2017 @05:44PM (#14102049)

Does not invalidate his main point: the developers have a conflict of interest into releasing features for the open source version that competes with the paid version.

[ Parent | on HN ]

Re:HTTP/2 is not the future, it’s the present by juliangoldsmith on Thursday April 13, 2017 @09:30AM (#14106656)

My reply wasn't intended to. I was pointing out that even the Plus version doesn't have Server Push. I don't expect it will ever be present in the open source version, barring a fork.

[ Parent | on HN ]

Re:HTTP/2 is not the future, it’s the present by pcollins123 on Thursday April 13, 2017 @10:13AM (#14107057)

I'm not sure they will ever implement it actually. Nginx does not support HTTP/2 server push as of March 2017 (v1.11).

Owen Garrett at nginx has summarized the reasons as follows:

- it is a non-essential and optional part of http/2

- if the client already has the resource cached, then by pushing it to them you might be unnecessarily wasting bandwidth.

- server push spec might change in the future.

- Link headers as hints is useful, but usage has been low from web developers.

- server push has been available as part of SPDY and was not utilized by many web developers.

Read his original comments here[1]. This table[2] accurately describes the pro's and con's of server hints vs server push.

Personally this disappoints me because I think this would be a valuable feature for web developers willing to invest the time to optimize page speeds. I also know that some large CDN's like Cloudflare have implemented their own version within nginx to optimize page downloads.

[1]: https://www.nginx.com/blog/http2-r7/

[2]: https://www.chromium.org/spdy/link-headers-and-server-hint

[ Parent | on HN ]