Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP/2 HTTP/3 support? #11019

Closed
khteh opened this issue Oct 18, 2021 · 3 comments
Closed

HTTP/2 HTTP/3 support? #11019

khteh opened this issue Oct 18, 2021 · 3 comments

Comments

@khteh
Copy link

khteh commented Oct 18, 2021

Launching quasar dev locally shows that it is on HTTP/1.1 GitHub page is using HTTP/2 though.
How to enable support for HTTP/2? If it doesn't at the moment, any plan to support HTTP/2 and/or HTTP/3?

@hawkeye64
Copy link
Member

quasar dev uses the package webpack-dev-server.
You should look at that site and ask on their repo.
Quasar will support it if they do.

https://webpack.js.org/configuration/dev-server/
https://github.com/webpack/webpack-dev-server#readme

@khteh
Copy link
Author

khteh commented Oct 19, 2021

It works with the following quasar.conf.js using self-signed cert:

    devServer: {
      http2: true,
      https: {
        key: fs.readFileSync('server.key'),
        cert: fs.readFileSync('server.crt'),
      },

However, some node packages are using deprecated symbols:

(node:155094) [DEP0066] DeprecationWarning: OutgoingMessage.prototype._headers is deprecated
(node:157424) [DEP0111] DeprecationWarning: Access to process.binding('http_parser') is deprecated.

@rstoenescu
Copy link
Member

@khteh Those warnings should be reported to webpack-dev-server. Those are not Quasar code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants