Skip to content

Fix expect 100 continue logic in Kestrel to avoid doing sync over async #31225

Closed

Description

@davidfowl

Describe the bug

Though this doesn't cause any problems in practice (we believe), there's a code cleanup that needs to happen around expect 100 continue handling in Kestrel. The code paths ProduceContinue are called from are all asynchronous, yet the method is synchronous and does sync over async. Lets fix that finally.

Here's the code

Activity

  1. added
    help wantedUp for grabs. We would accept a PR to help resolve this issue
    on Mar 25, 2021
  2. davidfowl commented on Mar 26, 2021

    @davidfowl
    MemberAuthor

    @wtgodbe assigned this to you for the next preview.

  3. ghost locked as resolved and limited conversation to collaborators on May 13, 2021
  4. added
    bugThis issue describes a behavior which is not expected - a bug.
    on May 14, 2021
  5. added
    area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
    and removed on Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsbugThis issue describes a behavior which is not expected - a bug.feature-kestrelhelp wantedUp for grabs. We would accept a PR to help resolve this issue

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions