h2 & server PUSH

[Louis Chanouha]

Hello,

If I'm right (I may have missed some exchanges in mailing), h2 main
improvement in 1.9  will be end2end working. So to have an h2 with
Server Push, we will need to have h2 enabled backends.

Is a server push initiated by HAProxy based on "Link" header scheduled
to 1.9 (like nginx http2_push_preload
<http://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_push_preload>
and h2o http2-push-preload) ?
<https://h2o.examp1e.net/configure/http2_directives.html#http2-push-preload>

Since a lot of CMS (& others apps) implement this header (and easyly
added manually if not), this is IMHO the fastest way to enable server
push even with h1 backends. It avoids upgrading backends and if you have
a cache server like me (eg Varnish, or HAProxy's internal), it is
useless to send data from backends.

Thanks for your answer & sorry for my english,

Louis

[Igor Cicimov]

Post by Louis Chanouha
Hello,
If I'm right (I may have missed some exchanges in mailing), h2 main
improvement in 1.9 will be end2end working. So to have an h2 with Server
Push, we will need to have h2 enabled backends.
Is a server push initiated by HAProxy based on "Link" header scheduled to
1.9 (like nginx http2_push_preload
<http://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_push_preload>
and h2o http2-push-preload) ?
<https://h2o.examp1e.net/configure/http2_directives.html#http2-push-preload>
Since a lot of CMS (& others apps) implement this header (and easyly added
manually if not), this is IMHO the fastest way to enable server push even
with h1 backends. It avoids upgrading backends and if you have a cache
server like me (eg Varnish, or HAProxy's internal), it is useless to send
data from backends.

Yes but then the proxy needs to parse the backend responses in order to
find the content to push so sounds like there would be a speed penalty for
this to work.

Post by Louis Chanouha
Thanks for your answer & sorry for my english,
Louis