Class HttpRule

Namespace: Temporalio.Api.Dependencies.Google.Api

Assembly: Temporalio.dll

gRPC Transcoding

gRPC Transcoding is a feature for mapping between a gRPC method and one or more HTTP REST endpoints. It allows developers to build a single API service that supports both gRPC APIs and REST APIs. Many systems, including Google APIs, Cloud Endpoints, gRPC Gateway, and Envoy proxy support this feature and use it for large scale production services.

HttpRule defines the schema of the gRPC/REST mapping. The mapping specifies how different portions of the gRPC request message are mapped to the URL path, URL query parameters, and HTTP request body. It also controls how the gRPC response message is mapped to the HTTP response body. HttpRule is typically specified as an google.api.http annotation on the gRPC method.

Each mapping specifies a URL path template and an HTTP method. The path template may refer to one or more fields in the gRPC request message, as long as each field is a non-repeated field with a primitive (non-message) type. The path template controls how fields of the request message are mapped to the URL path.

Example:

service Messaging {
  rpc GetMessage(GetMessageRequest) returns (Message) {
    option (google.api.http) = {
        get: "/v1/{name=messages/*}"
    };
  }
}
message GetMessageRequest {
  string name = 1; // Mapped to URL path.
}
message Message {
  string text = 1; // The resource content.
}

This enables an HTTP REST to gRPC mapping as below:

HTTP	gRPC
`GET /v1/messages/123456`	`GetMessage(name: "messages/123456")`

Any fields in the request message which are not bound by the path template automatically become HTTP query parameters if there is no HTTP request body. For example:

service Messaging {
  rpc GetMessage(GetMessageRequest) returns (Message) {
    option (google.api.http) = {
        get:"/v1/messages/{message_id}"
    };
  }
}
message GetMessageRequest {
  message SubMessage {
    string subfield = 1;
  }
  string message_id = 1; // Mapped to URL path.
  int64 revision = 2;    // Mapped to URL query parameter `revision`.
  SubMessage sub = 3;    // Mapped to URL query parameter `sub.subfield`.
}

This enables a HTTP JSON to RPC mapping as below:

HTTP | gRPC -----|----- GET /v1/messages/123456?revision=2&sub.subfield=foo | GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield: "foo"))

Note that fields which are mapped to URL query parameters must have a primitive type or a repeated primitive type or a non-repeated message type. In the case of a repeated type, the parameter can be repeated in the URL as ...?param=A&param=B. In the case of a message type, each field of the message is mapped to a separate parameter, such as ...?foo.a=A&foo.b=B&foo.c=C.

For HTTP methods that allow a request body, the body field specifies the mapping. Consider a REST update method on the message resource collection:

service Messaging {
  rpc UpdateMessage(UpdateMessageRequest) returns (Message) {
    option (google.api.http) = {
      patch: "/v1/messages/{message_id}"
      body: "message"
    };
  }
}
message UpdateMessageRequest {
  string message_id = 1; // mapped to the URL
  Message message = 2;   // mapped to the body
}

The following HTTP JSON to RPC mapping is enabled, where the representation of the JSON in the request body is determined by protos JSON encoding:

HTTP	gRPC
`PATCH /v1/messages/123456 { "text": "Hi!" }`	`UpdateMessage(message_id: "123456" message { text: "Hi!" })`

The special name * can be used in the body mapping to define that every field not bound by the path template should be mapped to the request body. This enables the following alternative definition of the update method:

service Messaging {
  rpc UpdateMessage(Message) returns (Message) {
    option (google.api.http) = {
      patch: "/v1/messages/{message_id}"
      body: "*"
    };
  }
}
message Message {
  string message_id = 1;
  string text = 2;
}

The following HTTP JSON to RPC mapping is enabled:

HTTP	gRPC
`PATCH /v1/messages/123456 { "text": "Hi!" }`	`UpdateMessage(message_id: "123456" text: "Hi!")`

Note that when using * in the body mapping, it is not possible to have HTTP parameters, as all fields not bound by the path end in the body. This makes this option more rarely used in practice when defining REST APIs. The common usage of * is in custom methods which don't use the URL at all for transferring data.

It is possible to define multiple HTTP methods for one RPC by using the additional_bindings option. Example:

service Messaging {
  rpc GetMessage(GetMessageRequest) returns (Message) {
    option (google.api.http) = {
      get: "/v1/messages/{message_id}"
      additional_bindings {
        get: "/v1/users/{user_id}/messages/{message_id}"
      }
    };
  }
}
message GetMessageRequest {
  string message_id = 1;
  string user_id = 2;
}

This enables the following two alternative HTTP JSON to RPC mappings:

HTTP	gRPC
`GET /v1/messages/123456`	`GetMessage(message_id: "123456")`
`GET /v1/users/me/messages/123456`	`GetMessage(user_id: "me" message_id: "123456")`

Rules for HTTP mapping

Leaf request fields (recursive expansion nested messages in the request message) are classified into three categories:
- Fields referred by the path template. They are passed via the URL path.
- Fields referred by the [HttpRule.body][google.api.HttpRule.body]. They are passed via the HTTP request body.
- All other fields are passed via the URL query parameters, and the parameter name is the field path in the request message. A repeated field can be represented as multiple query parameters under the same name.
If [HttpRule.body][google.api.HttpRule.body] is "*", there is no URL query parameter, all fields are passed via URL path and HTTP request body.
If [HttpRule.body][google.api.HttpRule.body] is omitted, there is no HTTP request body, all fields are passed via URL path and URL query parameters.

Path template syntax

Template = "/" Segments [ Verb ] ;
Segments = Segment { "/" Segment } ;
Segment  = "*" | "**" | LITERAL | Variable ;
Variable = "{" FieldPath [ "=" Segments ] "}" ;
FieldPath = IDENT { "." IDENT } ;
Verb     = ":" LITERAL ;

The syntax * matches a single URL path segment. The syntax ** matches zero or more URL path segments, which must be the last part of the URL path except the Verb.

The syntax Variable matches part of the URL path as specified by its template. A variable template must not contain other variables. If a variable matches a single path segment, its template may be omitted, e.g. {var} is equivalent to {var=*}.

The syntax LITERAL matches literal text in the URL path. If the LITERAL contains any reserved character, such characters should be percent-encoded before the matching.

If a variable contains exactly one path segment, such as "{var}" or "{var=*}", when such a variable is expanded into a URL path on the client side, all characters except [-_.~0-9a-zA-Z] are percent-encoded. The server side does the reverse decoding. Such variables show up in the Discovery Document as {var}.

If a variable contains multiple path segments, such as "{var=foo/*}" or "{var=**}", when such a variable is expanded into a URL path on the client side, all characters except [-_.~/0-9a-zA-Z] are percent-encoded. The server side does the reverse decoding, except "%2F" and "%2f" are left unchanged. Such variables show up in the Discovery Document as {+var}.

Using gRPC API Service Configuration

gRPC API Service Configuration (service config) is a configuration language for configuring a gRPC service to become a user-facing product. The service config is simply the YAML representation of the google.api.Service proto message.

As an alternative to annotating your proto file, you can configure gRPC transcoding in your service config YAML files. You do this by specifying a HttpRule that maps the gRPC method to a REST endpoint, achieving the same effect as the proto annotation. This can be particularly useful if you have a proto that is reused in multiple services. Note that any transcoding specified in the service config will override any matching transcoding configuration in the proto.

Example:

http:
  rules:
    # Selects a gRPC method and applies HttpRule to it.
    - selector: example.v1.Messaging.GetMessage
      get: /v1/messages/{message_id}/{sub.subfield}

Special notes

When gRPC Transcoding is used to map a gRPC to JSON REST endpoints, the proto to JSON conversion must follow the proto3 specification.

While the single segment variable follows the semantics of RFC 6570 Section 3.2.2 Simple String Expansion, the multi segment variable does not follow RFC 6570 Section 3.2.3 Reserved Expansion. The reason is that the Reserved Expansion does not expand special characters like ? and #, which would lead to invalid URLs. As the result, gRPC Transcoding uses a custom encoding for multi segment variables.

The path variables must not refer to any repeated or mapped field, because client libraries are not capable of handling such variable expansion.

The path variables must not capture the leading "/" character. The reason is that the most common use case "{var}" does not capture the leading "/" character. For consistency, all path variables must share the same behavior.

Repeated message fields must not be mapped to URL query parameters, because no client library can support such complicated mapping.

If an API needs to use a JSON array for request or response body, it can map the request or response body to a repeated field. However, some gRPC Transcoding implementations may not support this feature.

public sealed class HttpRule : IMessage<HttpRule>, IEquatable<HttpRule>, IDeepCloneable<HttpRule>, IBufferMessage, IMessage

Inheritance: object

HttpRule

Implements: IMessage<HttpRule>

IEquatable<HttpRule>

IDeepCloneable<HttpRule>

IBufferMessage

IMessage

Inherited Members: object.Equals(object, object)

object.GetType()

object.ReferenceEquals(object, object)

Constructors

HttpRule()

public HttpRule()

HttpRule(HttpRule)

public HttpRule(HttpRule other)

Parameters

other HttpRule

Fields

AdditionalBindingsFieldNumber

Field number for the "additional_bindings" field.

public const int AdditionalBindingsFieldNumber = 11

Field Value

int

BodyFieldNumber

Field number for the "body" field.

public const int BodyFieldNumber = 7

Field Value

int

CustomFieldNumber

Field number for the "custom" field.

public const int CustomFieldNumber = 8

Field Value

int

DeleteFieldNumber

Field number for the "delete" field.

public const int DeleteFieldNumber = 5

Field Value

int

GetFieldNumber

Field number for the "get" field.

public const int GetFieldNumber = 2

Field Value

int

PatchFieldNumber

Field number for the "patch" field.

public const int PatchFieldNumber = 6

Field Value

int

PostFieldNumber

Field number for the "post" field.

public const int PostFieldNumber = 4

Field Value

int

PutFieldNumber

Field number for the "put" field.

public const int PutFieldNumber = 3

Field Value

int

ResponseBodyFieldNumber

Field number for the "response_body" field.

public const int ResponseBodyFieldNumber = 12

Field Value

int

SelectorFieldNumber

Field number for the "selector" field.

public const int SelectorFieldNumber = 1

Field Value

int

Properties

AdditionalBindings

Additional HTTP bindings for the selector. Nested bindings must not contain an additional_bindings field themselves (that is, the nesting may only be one level deep).

public RepeatedField<HttpRule> AdditionalBindings { get; }

Property Value

RepeatedField<HttpRule>

Body

The name of the request field whose value is mapped to the HTTP request body, or * for mapping all request fields not captured by the path pattern to the HTTP body, or omitted for not having any HTTP request body.

NOTE: the referred field must be present at the top-level of the request message type.

public string Body { get; set; }

Property Value

string

Custom

The custom pattern is used for specifying an HTTP method that is not included in the pattern field, such as HEAD, or "*" to leave the HTTP method unspecified for this rule. The wild-card rule is useful for services that provide content to Web (HTML) clients.

public CustomHttpPattern Custom { get; set; }

Property Value

CustomHttpPattern

Delete

Maps to HTTP DELETE. Used for deleting a resource.

public string Delete { get; set; }

Property Value

string

Descriptor

public static MessageDescriptor Descriptor { get; }

Property Value

MessageDescriptor

Get

Maps to HTTP GET. Used for listing and getting information about resources.

public string Get { get; set; }

Property Value

string

HasDelete

Gets whether the "delete" field is set

public bool HasDelete { get; }

Property Value

bool

HasGet

Gets whether the "get" field is set

public bool HasGet { get; }

Property Value

bool

HasPatch

Gets whether the "patch" field is set

public bool HasPatch { get; }

Property Value

bool

HasPost

Gets whether the "post" field is set

public bool HasPost { get; }

Property Value

bool

HasPut

Gets whether the "put" field is set

public bool HasPut { get; }

Property Value

bool

Parser

public static MessageParser<HttpRule> Parser { get; }

Property Value

MessageParser<HttpRule>

Patch

Maps to HTTP PATCH. Used for updating a resource.

public string Patch { get; set; }

Property Value

string

PatternCase

public HttpRule.PatternOneofCase PatternCase { get; }

Property Value

HttpRule.PatternOneofCase

Post

Maps to HTTP POST. Used for creating a resource or performing an action.

public string Post { get; set; }

Property Value

string

Put

Maps to HTTP PUT. Used for replacing a resource.

public string Put { get; set; }

Property Value

string

ResponseBody

Optional. The name of the response field whose value is mapped to the HTTP response body. When omitted, the entire response message will be used as the HTTP response body.

NOTE: The referred field must be present at the top-level of the response message type.

public string ResponseBody { get; set; }

Property Value

string

Selector

Selects a method to which this rule applies.

Refer to [selector][google.api.DocumentationRule.selector] for syntax details.

public string Selector { get; set; }

Property Value

string

Methods

CalculateSize()

Calculates the size of this message in Protocol Buffer wire format, in bytes.

public int CalculateSize()

Returns

int: The number of bytes required to write this message to a coded output stream.

ClearDelete()

Clears the value of the oneof if it's currently set to "delete"

public void ClearDelete()

ClearGet()

Clears the value of the oneof if it's currently set to "get"

public void ClearGet()

ClearPatch()

Clears the value of the oneof if it's currently set to "patch"

public void ClearPatch()

ClearPattern()

public void ClearPattern()

ClearPost()

Clears the value of the oneof if it's currently set to "post"

public void ClearPost()

ClearPut()

Clears the value of the oneof if it's currently set to "put"

public void ClearPut()

Clone()

Creates a deep clone of this object.

public HttpRule Clone()

Returns

HttpRule: A deep clone of this object.

Equals(object)

Determines whether the specified object is equal to the current object.

public override bool Equals(object other)

Parameters

other object

Returns

bool: true if the specified object is equal to the current object; otherwise, false.

Equals(HttpRule)

Indicates whether the current object is equal to another object of the same type.

public bool Equals(HttpRule other)

Parameters

other HttpRule: An object to compare with this object.

Returns

bool: true if the current object is equal to the other parameter; otherwise, false.

GetHashCode()

Serves as the default hash function.

public override int GetHashCode()

Returns

int: A hash code for the current object.

MergeFrom(CodedInputStream)

Merges the data from the specified coded input stream with the current message.

public void MergeFrom(CodedInputStream input)

Parameters

input CodedInputStream

Remarks

See the user guide for precise merge semantics.

MergeFrom(HttpRule)

Merges the given message into this one.

public void MergeFrom(HttpRule other)

Parameters

other HttpRule

Remarks

See the user guide for precise merge semantics.

ToString()

Returns a string that represents the current object.

public override string ToString()

Returns

string: A string that represents the current object.

WriteTo(CodedOutputStream)

Writes the data to the given coded output stream.

public void WriteTo(CodedOutputStream output)

Parameters

output CodedOutputStream: Coded output stream to write the data to. Must not be null.

Table of Contents

Class HttpRule

gRPC Transcoding

Rules for HTTP mapping

Path template syntax

Using gRPC API Service Configuration

Special notes

Constructors

HttpRule()

HttpRule(HttpRule)

Parameters

Fields

AdditionalBindingsFieldNumber

Field Value

BodyFieldNumber

Field Value

CustomFieldNumber

Field Value

DeleteFieldNumber

Field Value

GetFieldNumber

Field Value

PatchFieldNumber

Field Value

PostFieldNumber

Field Value

PutFieldNumber

Field Value

ResponseBodyFieldNumber

Field Value

SelectorFieldNumber

Field Value

Properties

AdditionalBindings

Property Value

Body

Property Value

Custom

Property Value

Delete

Property Value

Descriptor

Property Value

Get

Property Value

HasDelete

Property Value

HasGet

Property Value

HasPatch

Property Value

HasPost

Property Value

HasPut

Property Value

Parser

Property Value

Patch

Property Value

PatternCase

Property Value

Post

Property Value

Put

Property Value

ResponseBody

Property Value

Selector

Property Value

Methods

CalculateSize()

Returns

ClearDelete()

ClearGet()

ClearPatch()

ClearPattern()

ClearPost()

ClearPut()

Clone()

Returns