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

Support per-vu TLS configuration for HTTP #3315

Closed
oleiade opened this issue Aug 30, 2023 · 2 comments
Closed

Support per-vu TLS configuration for HTTP #3315

oleiade opened this issue Aug 30, 2023 · 2 comments
Labels
feature new-http issues that would require (or benefit from) a new HTTP API

Comments

@oleiade
Copy link
Member

oleiade commented Aug 30, 2023

Feature Description

A user case for having the ability to have a per-vu TLS configuration for HTTP was recently reported to us.

With v0.46, we have introduced the ability to configure TLS per-vu for gRPC, and it might be worth considering doing that for HTTP, too. This could probably be part of the design considerations of the #2461 project.

This might be a duplicate, if so, please feel free to reference the original and close this.

Suggested Solution (optional)

No response

Already existing or connected issues / PRs (optional)

#2461

@oleiade oleiade added feature new-http issues that would require (or benefit from) a new HTTP API labels Aug 30, 2023
@codebien
Copy link
Contributor

codebien commented Aug 30, 2023

This should be the original issue for having TLS configurable #2186, we have closed it as it should be covered by the design doc. If this isn't the case then we should directly amend the design doc opening a PR.

@oleiade
Copy link
Member Author

oleiade commented Aug 31, 2023

Awesome, thanks a lot @codebien 🙇🏻 I'll close this one too then.

To anyone who might read this, we intend to address this in the next major version of our HTTP module, as per the existing design document, whose development can be tracked in #2461.

@oleiade oleiade closed this as completed Aug 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature new-http issues that would require (or benefit from) a new HTTP API
Projects
None yet
Development

No branches or pull requests

2 participants