Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page.
This message can be used both in streaming and non-streaming API methods in the request as well as the response.
It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body.
Example:
message GetResourceRequest {
// A unique request id.
string request_id = 1;
// The raw HTTP body is bound to this field.
google.api.HttpBody http_body = 2;
}
service ResourceService {
rpc GetResource(GetResourceRequest) returns (google.api.HttpBody);
rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty);
}
[[["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 2024-10-31 UTC."],[[["`HttpBody` is a message type used to represent arbitrary HTTP request or response bodies, especially for non-JSON formats like raw binary or HTML."],["It can be utilized in both streaming and non-streaming API methods, enabling flexible data transfer."],["`HttpBody` allows access to the raw HTTP body while also extracting parameters from URLs or HTTP templates."],["The fields within `HttpBody` include `content_type` for specifying the content type, `data` for holding the binary data, and `extensions` for application-specific metadata."]]],["The `HttpBody` message represents arbitrary HTTP content, useful for non-JSON formats like binary or HTML. It's applicable in both streaming and non-streaming API methods, for requests and responses. Key actions involve binding raw HTTP content to the `http_body` field in requests. Services can utilize `HttpBody` in RPC calls for retrieving or updating resources. It contains three fields: `content_type` (string), `data` (bytes), and `extensions` (metadata). The use of this type only impacts how request/response bodies are handled.\n"]]