Lines Matching refs:a

5 // You may obtain a copy of the License at
26 // Defines the HTTP configuration for an API service. It contains a list of
46 // gRPC Transcoding is a feature for mapping between a gRPC method and one or
47 // more HTTP REST endpoints. It allows developers to build a single API service
61 // Each mapping specifies a URL path template and an HTTP method. The path
63 // as each field is a non-repeated field with a primitive (non-message) type.
109 // This enables a HTTP JSON to RPC mapping as below:
117 // Note that fields which are mapped to URL query parameters must have a
118 // primitive type or a repeated primitive type or a non-repeated message type.
119 // In the case of a repeated type, the parameter can be repeated in the URL
120 // as `...?param=A&param=B`. In the case of a message type, each field of the
121 // message is mapped to a separate parameter, such as
122 // `...?foo.a=A&foo.b=B&foo.c=C`.
124 // For HTTP methods that allow a request body, the `body` field
125 // specifies the mapping. Consider a REST update method on the
233 // The syntax `*` matches a single URL path segment. The syntax `**` matches
238 // template. A variable template must not contain other variables. If a variable
239 // matches a single path segment, its template may be omitted, e.g. `{var}`
246 // If a variable contains exactly one path segment, such as `"{var}"` or
247 // `"{var=*}"`, when such a variable is expanded into a URL path on the client
248 // side, all characters except `[-_.~0-9a-zA-Z]` are percent-encoded. The
254 // If a variable contains multiple path segments, such as `"{var=foo/*}"`
255 // or `"{var=**}"`, when such a variable is expanded into a URL path on the
256 // client side, all characters except `[-_.~/0-9a-zA-Z]` are percent-encoded.
265 // gRPC API Service Configuration (service config) is a configuration language
266 // for configuring a gRPC service to become a user-facing product. The
271 // transcoding in your service config YAML files. You do this by specifying a
272 // `HttpRule` that maps the gRPC method to a REST endpoint, achieving the same
274 // have a proto that is reused in multiple services. Note that any transcoding
282 //         # Selects a gRPC method and applies HttpRule to it.
288 // When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the
297 // to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
310 // If an API needs to use a JSON array for request or response body, it can map
311 // the request or response body to a repeated field. However, some gRPC
314   // Selects a method to which this rule applies.
327     // Maps to HTTP PUT. Used for replacing a resource.
330     // Maps to HTTP POST. Used for creating a resource or performing an action.
333     // Maps to HTTP DELETE. Used for deleting a resource.
336     // Maps to HTTP PATCH. Used for updating a resource.