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

Ramp up HTTP/3 interop tests #19972

Closed
analogrelay opened this issue Mar 18, 2020 · 4 comments
Closed

Ramp up HTTP/3 interop tests #19972

analogrelay opened this issue Mar 18, 2020 · 4 comments
Labels
affected-very-few This issue impacts very few customers area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions HTTP3 severity-nice-to-have This label is used by an internal tool task
Milestone

Comments

@analogrelay
Copy link
Contributor

analogrelay commented Mar 18, 2020

Epic #15271

We need to ramp up some of our existing interop tests to support HTTP/3, once we have an end-to-end working for HTTP/3 between HttpClient and Kestrel.

Edit: These are first party clients and servers we should have at least some HTTP/3 interop testing with:

  • HttpClinet
  • Kestrel
  • HttpSys
  • IIS
  • WinHttp
@shirhatti shirhatti added this to the Next sprint planning milestone Mar 20, 2020
@jkotalik jkotalik added affected-very-few This issue impacts very few customers severity-nice-to-have This label is used by an internal tool task labels Nov 13, 2020 — with ASP.NET Core Issue Ranking
@JamesNK JamesNK added the HTTP3 label Dec 2, 2020
@jkotalik jkotalik modified the milestones: Backlog, Next sprint planning Dec 4, 2020
@ghost
Copy link

ghost commented Dec 4, 2020

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@adityamandaleeka
Copy link
Member

Some HttpClient testing against Kestrel is already in place.

Backlogging this for now.

@ghost
Copy link

ghost commented Aug 5, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@adityamandaleeka
Copy link
Member

Only gap seems to be Kestrel + different client, which is now covered in another issue. Closing this.

@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2021
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Jun 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affected-very-few This issue impacts very few customers area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions HTTP3 severity-nice-to-have This label is used by an internal tool task
Projects
None yet
Development

No branches or pull requests

7 participants