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.

Settings or Preferences | Editor | Inspections | Inappropriate gRPC request scheme

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

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection GrpcSchemes

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

Inspection Details
By default bundled with:	GoLand 2025.2, IntelliJ IDEA 2025.2, JetBrains Rider 2025.2, Qodana for .NET 2025.2, Qodana for Go 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025