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, 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-03-24 UTC."],[[["The latest version of the `BackendService.Types.Protocol` is 3.6.0, and the documentation provides access to various historical versions, starting from version 1.0.0 up to the most recent one."],["The `BackendService.Types.Protocol` enum defines the communication protocol used by the backend service, with supported options including `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, `Udp`, `UndefinedProtocol`, and `Unspecified`."],["The protocol chosen will change the kind of load balancing capabilities the backend service will be able to support."],["The `Unspecified` protocol allows the Backend Service to be used with any L3/L4 Forwarding Rules."],["The `Grpc` protocol is specifically for Traffic Director, and must be set when the backend service is referenced by a URL map bound to a target gRPC proxy."]]],[]]
