Reference documentation and code samples for the Compute Engine v1 API enum BackendService.Types.Protocol.
The protocol this BackendService uses to communicate with backends. Possible values are HTTP, HTTPS, HTTP2, H2C, TCP, SSL, UDP or GRPC. depending on the chosen load balancer or Traffic Director configuration. Refer to the documentation for the load balancers or for Traffic Director for more information. Must be set to GRPC when the backend service is referenced by a URL map that is bound to target gRPC proxy.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-05 UTC."],[[["The latest version of the `BackendService.Types.Protocol` is 3.6.0, and the documentation provides access to versions ranging from 1.0.0 to the latest."],["`BackendService.Types.Protocol` is an enum used by the Compute Engine v1 API to define the communication protocol used between a `BackendService` and its backends, which includes options like HTTP, HTTPS, HTTP2, TCP, SSL, UDP, or GRPC."],["The enum `BackendService.Types.Protocol` defines specific protocol fields such as `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, `Udp`, `UndefinedProtocol`, and `Unspecified`, each with its designated use, like gRPC for Traffic Director or TCP for proxying."],["The `Unspecified` protocol can be utilized with any L3/L4 Forwarding Rules, while `Grpc` is specifically required when a backend service is connected to a URL map that targets a gRPC proxy."]]],[]]
