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 content provides documentation for the `BackendService.Types.Protocol` enum within the Google Cloud Compute Engine v1 API, specifically for .NET."],["The enum defines the various protocols a `BackendService` can use to communicate with backends, including `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, `Udp`, `UndefinedProtocol` and `Unspecified`."],["The documentation offers a detailed version history of the `BackendService.Types.Protocol` enum, ranging from version 1.0.0 to the latest version 3.6.0, allowing users to access the relevant documentation for their specific version."],["The `Unspecified` field indicates that a Backend Service with this protocol can be used with any L3/L4 Forwarding Rules."],["The `Grpc` protocol is available for Traffic Director, and the `Http2` protocol uses HTTP/2 with SSL."]]],[]]
