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."],[[["The latest version available for `Google.Cloud.Compute.V1.BackendService.Types.Protocol` is 3.6.0, with multiple previous versions accessible, ranging back to version 1.0.0."],["This documentation provides reference and code samples for the Compute Engine v1 API enum `BackendService.Types.Protocol`, detailing the protocols that can be used to communicate with backends."],["The `Protocol` enum can be one of the following values: `Grpc`, `Http`, `Http2`, `Https`, `Ssl`, `Tcp`, `Udp`, `UndefinedProtocol`, and `Unspecified`."],["The `Protocol` enum's `Unspecified` field enables the service to be used with any L3/L4 Forwarding Rules, and `Grpc` is available for Traffic Director."],["The specific meaning and use of each protocol listed can be found within the full documentation."]]],[]]
