"http://" to default to port 80 in gRPC endpoint

Our custom logic for gRPC endpoint parsing default "http" to 443, which is not compatible to how users would expect the URL spec to behave. I understand that the gRPC endpoint and URL spec are not the same thing but when an user writes the environment variable for gRPC with HTTP URL terminology, we should respect the default ports expected as per the standard URL RFC (needs link to RFC). Defaulting to port 443 does not bring any extra security, since the port itself does not mean TLS, it is just a convention - a service can perfectly run without TLS on port 443. IMO, going against the RFC is not user-friendly for default port convention.

This proposal is to change the expected port to 80 when the user specifies "http://" as the prefix for the gRPC endpoint: https://github.com/dapr/proposals/blob/main/20230627-S-sidecar-endpoint-tls.md#test-matrix

I would like to collect quantitative data about how the community feels one way or another.

👍 For this proposal
👎 To keep it as-is

Read the linked sidecar endpoint TLS test matrix and compare its HTTP-port expectations with the URL RFC behavior described here. Review the discussion and reaction tally; done means documenting a decision on whether http:// should imply port 80, rather than assuming the change is ready to implement.

Written by the indexing model from the issue text.