Lines Matching refs:body

57 // path, URL query parameters, and HTTP request body. It also controls how the
58 // gRPC response message is mapped to the HTTP response body. `HttpRule` is
90 // automatically become HTTP query parameters if there is no HTTP request body.
124 // For HTTP methods that allow a request body, the `body` field
132 //           body: "message"
138 //       Message message = 2;   // mapped to the body
142 // representation of the JSON in the request body is determined by
150 // The special name `*` can be used in the body mapping to define that
152 // request body.  This enables the following alternative definition of
159 //           body: "*"
176 // Note that when using `*` in the body mapping, it is not possible to
178 // the body. This makes this option more rarely used in practice when
213 //    - Fields referred by the [HttpRule.body][google.api.HttpRule.body]. They are passed via the H…
214 //      request body.
219 //  2. If [HttpRule.body][google.api.HttpRule.body] is "*", there is no URL query parameter, all fi…
220 //     are passed via URL path and HTTP request body.
221 //  3. If [HttpRule.body][google.api.HttpRule.body] is omitted, there is no HTTP request body, all
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
347   // body, or `*` for mapping all request fields not captured by the path
348   // pattern to the HTTP body, or omitted for not having any HTTP request body.
352   string body = 7;  field
355   // response body. When omitted, the entire response message will be used
356   // as the HTTP response body.