-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
k6 extension: New experimental HTTP API #2461
Comments
codebien
added
feature
new-http
issues that would require (or benefit from) a new HTTP API
labels
Mar 25, 2022
This was referenced Mar 31, 2022
This was referenced Sep 8, 2022
Closed
This was referenced Feb 27, 2023
This was referenced Mar 28, 2023
Closed
This was referenced Mar 28, 2023
codebien
moved this from Long term - Q1 2024+
to Short term - Q3 2023
in k6 open-source public roadmap
Jun 14, 2023
codebien
moved this from Short term - Q3 2023
to Long term - Q1 2024+
in k6 open-source public roadmap
Jun 15, 2023
Hi. |
Hey @saniyar-dev, |
As we agreed during a meeting, we need to ensure that at some point a new HTTP module covers a case from #1169 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Exploring problems and solutions for #2311 has shown us that trying to fix all the problems in the old API would require compromises that wouldn't solve the root cause of the issue.
To that end, we have decided to explore solutions for this and other HTTP-related issues in a new k6 extension. This will be an implementation of a new HTTP API, and will require changes in several core parts of k6.
We've come up with a design document for this work, with some initial ideas that would address most of these issues. The design is still very much in flux, and will likely change as the work progresses.
Task list
The text was updated successfully, but these errors were encountered: