http2

HTTP/2 priority & dependency test with Jetty

六月ゝ 毕业季﹏ 提交于 2019-12-11 11:33:31
问题 Priority & Dependency: Here I made I simple test. But the result seems not so good. I tried to make 100 request in a for loop in the same connection(the request url is the same, I am wondering whether this part influence the results). If the index is i, then my request stream_id is i while the dependent stream_id is 100+i. If our assumption is right, the request can never get response because there is no stream_id from 101 to 200. But the results shows there is no difference for setting the

Handshaker.algorithmConstraints

旧时模样 提交于 2019-12-11 11:31:51
问题 I am running the code Jetty provided for HTTP/2 client https://github.com/eclipse/jetty.project/blob/master/jetty-http2/http2-client/src/test/java/org/eclipse/jetty/http2/client/Client.java And I come across such a problem INFO::main: Logging initialized @166ms 2015-09-04 22:48:46.253:WARN:oejut.QueuedThreadPool:qtp1342443276-11: java.lang.IllegalAccessError: tried to access field sun.security.ssl.Handshaker.algorithmConstraints from class sun.security.ssl.ClientHandshaker at sun.security.ssl

Sending HTTP/2 POST request NodeJS

社会主义新天地 提交于 2019-12-11 06:01:10
问题 I'm trying to figure out how to send an HTTP/2 POST request with NodeJS. I have so far from the example in the documentation: const http2 = require('http2'); const fs = require('fs'); const client = http2.connect('https://localhost:8443', { ca: fs.readFileSync('localhost-cert.pem') }); client.on('error', (err) => console.error(err)); client.on('socketError', (err) => console.error(err)); const req = client.request({ ':path': '/' }); req.on('response', (headers, flags) => { for (const name in

HTTP2 Push- placing script tags in res.end

有些话、适合烂在心里 提交于 2019-12-11 05:42:59
问题 After reading HTTP2 Article using Speedy NPM module, I have a question. The benefit of HTTP2 push is that the browser has the resources cached before the browser requests them. In this example: spdy.createServer(options, function(req, res) { // push JavaScript asset (/main.js) to the client res.push('/main.js', {'content-type': 'application/javascript'}, function(err, stream) { stream.end('alert("hello from push stream!")'); }); // write main response body and terminate stream res.end('Hello

java.io.IOException: stream was reset: REFUSED_STREAM on several devices

安稳与你 提交于 2019-12-11 04:59:32
问题 I'm using Retrofit 1.9 in my Android app. Server is on Django with Nginx, HTTPS with HTTP 2. Certificate is from WoSign, "A" score on SSL Labs. I'm testing on 3 devices: Nexus 4, Android 5.1.1 (official) Nexus 9, Android 7.0 (official) Samsung Galaxy S3, Android 4.4 (official) On SGS3 it works fine, but on Nexus 4 & 9 I'm getting the exception: java.io.IOException: stream was reset: REFUSED_STREAM at com.squareup.okhttp.internal.framed.FramedStream.getResponseHeaders(FramedStream.java:146) at

Can I stream a response back to the browser using http2?

二次信任 提交于 2019-12-11 04:55:57
问题 Is it possible to stream a response back to the browser, from node, perhaps using http2? In my web-app, a user presses a button which starts a server process. This process might take 10 minutes or longer to complete. I want to stream status updates back to the client/browser. I believe I can do this with websockets, but I was hoping http2 had something to make this easier. I know it supports "push" but as far as I know, that's only for pushing files the user might need in the future. Or maybe

Okhttp not selecting http2 on Android 7.0

混江龙づ霸主 提交于 2019-12-11 04:39:53
问题 I am trying to make an HTTP request to the following domain (http2 enabled) on a device running on Android 7.0. The code i use is as follows: Request request = new Request.Builder() .url("https://http2.akamai.com/") .build(); response = okHttpClient.newCall(request).execute(); statusCode = response.code(); As I notice in the response object, the protocol used by okHttp is HTTP 1.1 The behavior of the okhttp client is random, at one time I was able to see the protocol as h2 but then repeating

Serving HTTP version of site to those who don't support HTTP2

最后都变了- 提交于 2019-12-11 03:57:50
问题 I'd like to move my client's site entirely to HTTPS in order to allow HTTP2 to work, however I was wondering is it ok (in the eyes of search engines) to serve older traffic (of which there is a lot and which would otherwise suffer a perf hit) that do not support HTTP2? Is this dangerous to do from an SEO point of view? and could you do the detection with tools like WURFL? I want to stay current and offer improved perf/security to those on newer browsers but don't want those on older browsers

Why is the stream identifier 31 bit in HTTP/2 and why is it preceded with a reserved bit?

ぃ、小莉子 提交于 2019-12-11 03:38:36
问题 The frame format in HTTP/2 looks like this (source: HTTP/2: Frame Format): +-----------------------------------------------+ | Length (24) | +---------------+---------------+---------------+ | Type (8) | Flags (8) | +-+-------------+---------------+-------------------------------+ |R| Stream Identifier (31) | +=+=============================================================+ | Frame Payload (0...) ... +---------------------------------------------------------------+ R : A reserved 1-bit field.

HTTP2 Request doesn't follow redirects in JMeter 5.0

筅森魡賤 提交于 2019-12-11 02:06:59
问题 I'm using the HTTP2 plugin for JMeter from Blazemeter and I'm unable to make the HTTP2 request follow the redirects. I tried checking the "Follow Redirects" box and "Synchronized Request" and it doesn't work. I get the Response code: 301 & Response message: HTTP/2.0 301 Moved Permanently and the location where it should redirect in the Response headers => "location". I am trying to make a HTTP2 request to "www.aoro.ro" (GET https://www.aoro.ro/) which should redirect me to "https://www.notino