Re: [jetty-dev] HTTP/2 Push is not working

[Guillaume Drouet <guidrouet@xxxxxxxxx>]

Ho you're totally right. HTTP/2 server push actualy works. The interesting point is that HTTP/2 is not always faster than a non secured HTTP/1.1 connection. This was curious when I compared response times of both connectors and this is mainly why I was not sure that server-push was working...

Thanks!

2015-04-21 21:33 GMT+02:00 Simone Bordet <sbordet@xxxxxxxxxxx>:

Hi,

On Tue, Apr 21, 2015 at 5:23 PM, Guillaume Drouet <guidrouet@xxxxxxxxx> wrote:
> Hi,
>
> yes it seems to work on https://webtide.com because I see in chrome that all
> statics are downloaded at the same time. I'm still surprised that chrome
> shows that they are required after the HTML page is fetched, but not sure
> this tool is fully reliable.
>
> My Chrome version is 43.0.2351.3 m
>
> No particular log reports something related to the internal push operations.
> However, the filter works has expected and calls the push() method for each
> associated resource.
>
> I make sure the browser makes a new request by putting a breakpoint in the
> filter. Each time a static is needed, I can see the browser actually makes a
> new request to the server instead of expecting the promised push.

Nah.
It's the internal, server-side only, push mechanism that makes these
request, not the browser.

Please use chrome://net-internals/#spdy to actually see what's going
on at the HTTP/2 level in the browser (click on the right connection
link).
You will see the stream of all HTTP/2 frames.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev

--

Guillaume DROUET