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-21 UTC."],[[["This page provides reference documentation for the `BackendService.Types.Protocol` enum in the Google Cloud Compute Engine v1 API, detailing its available protocol options for backend communication."],["The latest version documented is 3.6.0, while the current version that is being viewed is 2.9.0, which are part of a range of versions from 1.0.0 up to 3.6.0 that are provided in the linked list of versions."],["The `BackendService.Types.Protocol` enum defines various supported protocols, including `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, `Udp`, `UndefinedProtocol`, and `Unspecified`."],["The protocol options impact the type of load balancer or Traffic Director configuration that can be used, with `GRPC` being required when the backend service is referenced by a URL map bound to a target gRPC proxy."],["`Unspecified` protocol allows the backend service to be used with any L3/L4 Forwarding Rules, making it the most versatile option."]]],[]]
