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 page provides a comprehensive list of available versions for the `BackendService.Types.Protocol` enum within the Google Cloud Compute Engine v1 API, ranging from version 1.0.0 to the latest, 3.6.0."],["The `BackendService.Types.Protocol` enum specifies the protocol used by a BackendService to communicate with backends, including options like HTTP, HTTPS, HTTP2, TCP, SSL, UDP, or GRPC."],["The documentation details each protocol's purpose, such as `Grpc` being for Traffic Director, `Http2` for HTTP/2 with SSL, and `Ssl` for TCP proxying with SSL, among others."],["The latest version of the Google.Cloud.Compute.V1 is 3.6.0, and the current page is displaying details for version 2.15.0."],["There are special fields such as `UndefinedProtocol` which means the field is not set and `Unspecified` which means it can be used with any L3/L4 forwarding rules."]]],[]]
