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-04-09 UTC."],[[["This page provides reference documentation for the `BackendService.Types.Protocol` enum in the Google Cloud Compute Engine v1 API, specifically for .NET."],["The latest version documented is 3.6.0, with a comprehensive list of previous versions ranging from 3.5.0 down to 1.0.0, each linked to its respective documentation."],["The `BackendService.Types.Protocol` enum defines the communication protocols used by the BackendService, including `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, `Udp`, `UndefinedProtocol` and `Unspecified`."],["Each protocol is accompanied by a brief description, outlining its use cases such as gRPC for Traffic Director, TCP proxying or pass-through, or UDP, along with the `UndefinedProtocol` to specify a unset field and the `Unspecified` if the backend can be used with L3/L4 Forwarding rules."]]],[]]
