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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eThis page provides reference documentation for the \u003ccode\u003eBackendService.Types.Protocol\u003c/code\u003e enum in the Google Cloud Compute Engine v1 API, detailing its available protocol options for backend communication.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version documented is 3.6.0, while the current version that is being viewed is 2.9.0, which are part of a range of versions from 1.0.0 up to 3.6.0 that are provided in the linked list of versions.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eBackendService.Types.Protocol\u003c/code\u003e enum defines various supported protocols, including \u003ccode\u003eGrpc\u003c/code\u003e, \u003ccode\u003eHttp\u003c/code\u003e, \u003ccode\u003eHttp2\u003c/code\u003e, \u003ccode\u003eHttps\u003c/code\u003e, \u003ccode\u003eSsl\u003c/code\u003e, \u003ccode\u003eTcp\u003c/code\u003e, \u003ccode\u003eUdp\u003c/code\u003e, \u003ccode\u003eUndefinedProtocol\u003c/code\u003e, and \u003ccode\u003eUnspecified\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe protocol options impact the type of load balancer or Traffic Director configuration that can be used, with \u003ccode\u003eGRPC\u003c/code\u003e being required when the backend service is referenced by a URL map bound to a target gRPC proxy.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eUnspecified\u003c/code\u003e protocol allows the backend service to be used with any L3/L4 Forwarding Rules, making it the most versatile option.\u003c/p\u003e\n"]]],[],null,[]]
