Skip to content

fix(http): clarify HTTP/2 server compatibility with Connect app #20664

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

drjoeycadieux
Copy link

Resolves the TODO comment in resolveHttpServer by replacing @ts-expect-error with a proper type cast and explanatory comment.

When allowHTTP1: true is set, the HTTP/2 server can handle HTTP/1.1 requests, making the Connect app compatible as a request listener since:

  • Http2ServerRequest extends IncomingMessage
  • Http2ServerResponse extends ServerResponse
  • The server operates in HTTP/1.1 compatibility mode

This change improves code clarity and maintainability by removing the ambiguous TODO and explaining the type compatibility.

Description

Resolves the TODO comment in resolveHttpServer by replacing @ts-expect-error
with a proper type cast and explanatory comment.

When allowHTTP1: true is set, the HTTP/2 server can handle HTTP/1.1 requests,
making the Connect app compatible as a request listener since:
- Http2ServerRequest extends IncomingMessage
- Http2ServerResponse extends ServerResponse
- The server operates in HTTP/1.1 compatibility mode

This change improves code clarity and maintainability by removing the
ambiguous TODO and explaining the type compatibility.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant