Skip to content

Improve logging and error messages when mismatch between client and server protocol/TLS #14884

Open
@JamesNK

Description

@JamesNK

My experience with gRPC is that it is very common to run into trouble establishing a connection between the client and the server because of incorrect protocol/TLS.

The logging and error messages that Kestrel/IIS provides should do as much as possible to to help developers fix their own mistakes. Also I would like to make sure that we're sending the best response to clients in these situations to help the client give the developer a good understanding of what is wrong.

Common problem situations:

  1. Client (HTTP/2 with and without TLS) calling HTTP/1 only port
  2. Client (HTTP/1 with and without TLS) calling HTTP/2 only port
  3. Client (HTTP/2 without TLS) calling HTTP/1 and HTTP/2 port (will fail because no negotiation and default to 1.1)
  4. Client (no TLS) calling TLS port
  5. Client (TLS) calling no TLS port

Metadata

Metadata

Assignees

No one assigned

    Labels

    affected-very-fewThis issue impacts very few customersarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsenhancementThis issue represents an ask for new feature or an enhancement to an existing oneseverity-nice-to-haveThis label is used by an internal tool

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions