dotnet/aspnetcore

Ramp up HTTP/3 interop tests

analogrelay opened this issue · 4 comments

analogrelay commented

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
msftbot commented

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 commented
  • Browser testing should be covered by #34859
  • HTTP.SYS covered in part by #29077
  • IIS covered in part by #29078

Some HttpClient testing against Kestrel is already in place.

Backlogging this for now.

msftbot commented

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 commented

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