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 latest version of the Google.Cloud.Compute.V1 API for BackendService.Types.Protocol is 3.6.0, with multiple prior versions available dating back to version 1.0.0."],["The `Protocol` enum defines the communication protocols supported by a BackendService, including `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, and `Udp`."],["The `UndefinedProtocol` field indicates when the enum field is not set, and `Unspecified` means the Backend Service can be used with any L3/L4 Forwarding Rules."],["The `Grpc` protocol is available for Traffic Director, while `Http2` implies HTTP/2 with SSL, and `Ssl` represents TCP proxying with SSL."],["The documentation provides reference and code examples for the Compute Engine v1 API enum BackendService.Types.Protocol."]]],[]]
