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

HTTP2 with prior knowledge #2348

Closed
raoufkh opened this issue Jan 20, 2022 · 2 comments
Closed

HTTP2 with prior knowledge #2348

raoufkh opened this issue Jan 20, 2022 · 2 comments
Labels
evaluation needed proposal needs to be validated or tested before fully implementing it in k6 feature new-http issues that would require (or benefit from) a new HTTP API

Comments

@raoufkh
Copy link

raoufkh commented Jan 20, 2022

Feature Description

Hello

K6 docuementation says that k6 will automatically upgrade to HTTP2 if the server indicates its support for this protocol. However, I've tested with a server supporting this protocol, using this script and upgrading has not been done. So, is there a way to force the K6 client to use HTTP2 done with prior knowledge? Somehow what the --http2-prior-knowledge flag of the tool curl can do.

Bests,
Raouf

Suggested Solution (optional)

curl --http2-prior-knowledge

Already existing or connected issues / PRs (optional)

#970

@na--
Copy link
Member

na-- commented Jan 21, 2022

Since you linked #970, was the HTTP2 server you tried to connect to also h2c (unencrypted)?

@na-- na-- added awaiting user waiting for user to respond evaluation needed proposal needs to be validated or tested before fully implementing it in k6 labels Jan 21, 2022
@na-- na-- added new-http issues that would require (or benefit from) a new HTTP API and removed awaiting user waiting for user to respond labels Mar 18, 2022
@imiric
Copy link
Contributor

imiric commented Mar 28, 2023

We're unlikely to implement this in the current HTTP API, but it will be considered as part of the new API (initial design document). We're still ironing out the design and syntax, so you can follow the issue and document for details.

I'll close this issue in the meantime, as we want to keep a clean roadmap.

@imiric imiric closed this as completed Mar 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
evaluation needed proposal needs to be validated or tested before fully implementing it in k6 feature new-http issues that would require (or benefit from) a new HTTP API
Projects
None yet
Development

No branches or pull requests

3 participants