GRPC request schema can be substituted or omitted
Reports unnecessary `grpc` or standard `http[s]` schemes usage in gRPC requests
Example requests:
# `grpc` scheme may be omitted since insecure connection is assumed by default
GRPC grpc://localhost/TestService/testRpc
# `http` scheme may be omitted: prefer empty scheme for insecure connection and a dedicated `grpcs` scheme for a secure one
GRPC http://localhost/TestService/testRpc
# `https` scheme should be replaced by `grpcs`: prefer a dedicated `grpcs` scheme to indicate that transport layer security should be enabled to execute the request
GRPC https://localhost/TestService/testRpc
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
GrpcSchemes- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
To avoid confusion, it is recommended to use dedicated `grpcs` scheme in a gRPC request, when the request should use secure channel underneath. Otherwise, the scheme might be completely omitted
Availability
- By default bundled with
GoLand 2024.1, IntelliJ IDEA 2024.1, JetBrains Rider 2023.3, Qodana for .NET 2023.3, Qodana for Go 2024.1, Qodana for JVM 2024.1,
- Can be installed with plugin
gRPC, 241.18072
Last modified: 18 June 2024