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 Compute Engine v1 API, detailing the communication protocols used by backend services."],["The latest version of the documentation is 3.6.0, with a range of previous versions also available, spanning from 1.0.0 up to the most recent."],["The available protocols include `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, `Udp`, `UndefinedProtocol`, and `Unspecified`, each serving different networking needs."],["The `Unspecified` protocol allows the Backend Service to be used with any L3/L4 Forwarding Rules, offering flexibility in configuration."],["The `Grpc` protocol is specified for Traffic Director, while the `Http2` protocol is for HTTP/2 with SSL, each protocol having its own specific role and application within the context of Google Cloud's infrastructure."]]],[]]
