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 document provides reference information for the `BackendService.Types.Protocol` enum within the Google Cloud Compute Engine v1 API, listing all its available versions."],["The latest version of the API is 3.6.0, and the document includes versions from 1.0.0 up to the most recent, with the current version displayed as 2.14.0 at the top."],["The `BackendService.Types.Protocol` enum defines the communication protocols that a BackendService can use, including options like `Grpc`, `Http`, `Https`, `Tcp`, `Ssl`, and `Udp`."],["The documentation specifies that if a Backend Service has `UNSPECIFIED` as its protocol, it can be used with any L3/L4 Forwarding Rules."],["The `UndefinedProtocol` field of the enum indicates when a protocol field is not set, providing clarity on field status."]]],[]]
