http2

HTTP 2 will support server push, what does this mean?

淺唱寂寞╮ 提交于 2019-11-26 20:25:20
问题 I've read a lot of things about HTTP 2 (which is still in development), so I also heard about the server push feature, but I my head, this is not clear. Does this server push feature mean that the server will be able to send a response to the client without the latter making a request? Just like a vanilla TCP connection? Or I'm missing the point? 回答1: The HTTP2 push mechanism is not a generic server push mechanism like websocket or server sent events. It is designed for a specific

Optimizing File Cacheing and HTTP2

China☆狼群 提交于 2019-11-26 17:33:45
问题 Our site is considering making the switch to http2. My understanding is that http2 renders optimization techniques like file concatenation obsolete , since a server using http2 just sends one request. Instead, the advice I am seeing is that it's better to keep file sizes smaller so that they are more likely to be cached by a browser. It probably depends on the size of a website, but how small should a website's files be if its using http2 and wants to focus on caching? In our case, our many

The jdk.incubator.httpclient module not found in Java11

若如初见. 提交于 2019-11-26 16:55:16
问题 Using the early access build for JDK/11 to compile an existing code based on Java-9 which was using a VM argument --add-modules jdk.incubator.httpclient to resolve the HTTP/2 client incubator module now ends up with a compilation error Module not found: jdk.incubator.httpclient Java version details :- java 11-ea 2018-09-25 Java(TM) SE Runtime Environment 18.9 (build 11-ea+11) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+11, mixed mode) 回答1: With the standardization of the HTTP Client

HTTP2 with node.js behind nginx proxy

萝らか妹 提交于 2019-11-26 13:30:15
I have a node.js server running behind an nginx proxy. node.js is running an HTTP 1.1 (no SSL) server on port 3000. Both are running on the same server. I recently set up nginx to use HTTP2 with SSL (h2). It seems that HTTP2 is indeed enabled and working. However, I want to know whether the fact that the proxy connection (nginx <--> node.js) is using HTTP 1.1 affects performance. That is, am I missing the HTTP2 benefits in terms of speed because my internal connection is HTTP 1.1? In general, the biggest immediate benefit of HTTP/2 is the speed increase offered by multiplexing for the browser

What does multiplexing mean in HTTP/2

扶醉桌前 提交于 2019-11-26 12:16:23
Could someone please explain multiplexing in relation to HTTP/2 and how it works? Put simply, multiplexing allows your Browser to fire off multiple requests at once on the same connection and receive the requests back in any order. And now for the much more complicated answer... When you load a web page, it downloads the HTML page, it sees it needs some CSS, some JavaScript, a load of images... etc. Under HTTP/1.1 you can only download one of those at a time on your HTTP/1.1 connection. So your browser downloads the HTML, then it asks for the CSS file. When that's returned it asks for the

Does HTTP/2 make websockets obsolete?

喜夏-厌秋 提交于 2019-11-26 08:39:34
问题 I\'m learning about HTTP/2 protocol. It\'s a binary protocol with small message frames. It allows stream multiplexing over single TCP connection. Conceptually it seems very similar to WebSockets. Are there plans to obsolete websockets and replace them with some kind of headerless HTTP/2 requests and server-initiated push messages? Or will WebSockets complement HTTP/2? 回答1: From what I understood HTTP/2 is not a replacement for websocket but aims to standardize SPDY protocol. In HTTP/2, server

HTTP2 with node.js behind nginx proxy

空扰寡人 提交于 2019-11-26 03:28:36
问题 I have a node.js server running behind an nginx proxy. node.js is running an HTTP 1.1 (no SSL) server on port 3000. Both are running on the same server. I recently set up nginx to use HTTP2 with SSL (h2). It seems that HTTP2 is indeed enabled and working. However, I want to know whether the fact that the proxy connection (nginx <--> node.js) is using HTTP 1.1 affects performance. That is, am I missing the HTTP2 benefits in terms of speed because my internal connection is HTTP 1.1? 回答1: In

What does multiplexing mean in HTTP/2

◇◆丶佛笑我妖孽 提交于 2019-11-26 02:29:45
问题 Could someone please explain multiplexing in relation to HTTP/2 and how it works? 回答1: Put simply, multiplexing allows your Browser to fire off multiple requests at once on the same connection and receive the requests back in any order. And now for the much more complicated answer... When you load a web page, it downloads the HTML page, it sees it needs some CSS, some JavaScript, a load of images... etc. Under HTTP/1.1 you can only download one of those at a time on your HTTP/1.1 connection.