http2

I'm setting the Link header to preload an XHR request that happens on load. Link: </images/project_icon.png>; rel=preload; as=image,</db/xhr_stuff>; rel=preload Chrome 57.0 preloads and uses the /images/project_icon.png just fine but it preloads /db/xhr_stuff and then misses the copy it just retrieved and loads it a second time after the DOM completely loads. The request headers are identical except the one later one initiated by the xhr has x-requested-with:XMLHttpRequest set. The only other difference between the requests is the one initiated by the link header shows up as Type: json and the

In this way, the client can connect the server without ALPN and use http/2 default. Is that possible？ Yes it is possible, but the conditions are strict. Browsers, as of now, do not implement clear-text communication for HTTP/2, so if you use a browser the answer to your question is no: you have to deploy your server with ALPN support if you want browsers to be able to connect. On the other hand, other clients such as Java clients may be able to connect to a server using clear-text HTTP/2, so for those type of clients the answer to your question is yes: you can deploy a HTTP/2 server without

for SPDY, we need to implement a PushStrategy and to register it to push resources. What about HTTP2 support? I like the idea of nginx which consists to read link header in the HTTP response: https://nghttp2.org/blog/2015/02/10/nghttp2-dot-org-enabled-http2-server-push/ Thanks! Jetty HTTP/2 comes with full support for HTTP/2 Push, in fact in different flavors. Webtide's website already has Jetty's HTTP/2 Push enabled. There is a PushCacheFilter , which implements the same algorithm that was implemented in Jetty SPDY's PushStrategy, based on the Referer header. There is a PushSessionCacheFilter

So far all the tutorials tell me that I need to enable SSL on my server to have HTTP/2 support. In the given scenario, we have nginx in front of the backend Tomcat/Jetty server(s), and even though performance-wise it worth enabling HTTP/2 on the backend, the requirement to have HTTPS there as well seems to be an overkill. HTTPS is not needed security-wise (only nginx is exposed), and is a bit cumbersome from the operational perspective - we'd have to add our certificates to each of the Docker containers that run the backend servers. Isn't there a way around that provides HTTP/2 support all the

I'm creating a small chat application in gRPC right now and I've run into the issue where if a user wants to connect to the gRPC server as a client, I'd like to broadcast that the event has occurred to all other connected clients. I'm thinking of using some sort of observer but I"m confused as to how the server knows of who is connected and how I would broadcast the event to all clients and not just one or two. I know using streams is part of the answer, but because each client is creating it's own stream with the server, I'm unsure of how it can subscribe to other server-client streams. Yup,

We have recently shifted from HTTP to HTTPS. As we have already moved to HTTPS, we are thinking of moving to HTTP/2 to get performance benefits. As explained above that requests between browser and LB are secured (HTTPS) while communication between LB and app server still using HTTP What is the possibility of enabling HTTP /2 with the current setup? Can we enable HTTP/2 between browser and LB while communication between LB and app servers remain on HTTP? HAProxy 1.8 supports HTTP/2 From the 1.8 announcement : HAProxy 1.8 now supports HTTP/2 on the client side (in the frontend sections) and can

We have many React Native <Image> components rendering per screen and are witnessing performance issues due to many simultaneous http requests . Opening and closing a connection is expensive, and having too many simultaneous connections can hit limitations that cause timeouts. HTTP/2 features multiplexing , allowing multiple requests and response messages between the client and server to be in flight at the same time over a single connection, instead of multiple connections, which improves page load times. CloudFront supports HTTP/2, HTTP/1.1, and HTTP/1 by default depending on the version the