Allow h2c usage on localhost
Reported by
joan.kar...@gmail.com,
Nov 27
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36 Steps to reproduce the problem: Run Selenium tests or develop on localhost. What is the expected behavior? I know HTTP2 is only intended to work over TLS in browsers. But I'd like to make the argument for using HTTP2 over TCP when accessing localhost. Working with self-signed certificates is not ideal and this will improve the performance during web development and for things like Selenium tests. What went wrong? HTTP2 can only be used over TLS even for local connections. Did this work before? No Does this work in other browsers? No Chrome version: 70.0.3538.110 Channel: stable OS Version: 10.0 Flash Version:
,
Nov 27
,
Nov 27
Seems not worth the effort to just support H2 over localhost only, but I'll defer to others on making a call here.
,
Nov 28
Thanks for filing the issue! From comment#0, it is understood that this seems to be triaged by running Selenium tests, which is out of scope for us to do it from our end. Hence adding label "TE-NeedsTriageHelp" and requesting some one from "Internals>Network>HTTP2" team to have a look a into it for further inputs.
,
Nov 28
I do not support this change. I agree that it is not worth the effort, as mentioned in comment #3. Also note that many other web features are restricted to secure connections as well. As the ecosystem is moving towards secure connections, it is going to be inevitable for developers to set up their testing environment accordingly, and making an exemption for HTTP/2 will not hold up this process. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by dtapu...@chromium.org
, Nov 27