http2 does not work
See original GitHub issueSetting HTTP_VERSION
option to CURL_HTTP_VERSION_2_PRIOR_KNOWLEDGE
still sends http1.1 request.
I tried with Curl:
curl.setOpt('URL', 'http://localhost:3000'); curl.setOpt('HTTP_VERSION', 'CURL_HTTP_VERSION_2_PRIOR_KNOWLEDGE');
And with curly:
const response = await curly.get('http://localhost:3000', { HTTP_VERSION: 'CURL_HTTP_VERSION_2_PRIOR_KNOWLEDGE' })
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
HTTP/2 not working on browsers | Plesk Forum
Hello, I have spent a couple of days trying to set up http/2 for my website. I also performed all troubleshooting available on...
Read more >Enabling http/2 in Apache 2.4 does not work - Stack Overflow
No errors in log files, the server restarts without no problems or errors. Access website with https:// works, but browser always downgrades ...
Read more >Why http2 doesn't work on my Apache/2.4.29? - Server Fault
Starting from Apache 2.4.27, the Apache MPM (Multi-Processing Module) prefork no longer supports HTTP/2. This will be indicated in your Apache ...
Read more >Nginx's HTTP/2 Does Not Work - 4devs
Problems with HTTP/2 in Nginx and possible solutions.
Read more >HTTP/2 guide - Apache HTTP Server Version 2.4
HTTP/2 is able to run multiple streams of data over the same TCP connection, avoiding the classic HTTP 1.1 head of blocking slow...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I see, those names on libcurl documentation are C constants declared by libcurl, if you see them in other options they probably have a corresponding object in this library, if they don’t or the option is not supported, or we have a missing option, which should be reported.
CURLMOPT_PUSHFUNCTION
is currently not supported by the binding, so it’s not possible to accept push_promise frames currently. If you think this would be a great feature to have please create a new issue with the feature request and I should be able to take a look into it next week (or if you can, pull requests implementing it are also welcome)