HTTP GET with query params error

[jackwener]

grpc-gateway/third_party/googleapis/google/api/http.proto

Line 117 in ead3fc0

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

I found it is supported in above document.

but something went wrong in practice

phenomenon

get: /dyeing/appid/{appid}/id_type/{id_type}?page_num={page_num}&page_size={page_size}

error

--grpc-gateway_out: unexpected token "?page_num=" after segments "dyeing/appid/{appid}/id_type/{id_type}": /dyeing/appid/{appid}/id_type/{id_type}?page_num={page_num}&page_size={page_size}

[johanbrandhorst]

Hi again @jackwener, in the future could you please join the support channel on Gophers slack (#grpc-gateway) like the issue template asks? This is not a bug but a simple misunderstanding.

See

grpc-gateway/third_party/googleapis/google/api/http.proto

Lines 93 to 95 in ead3fc0

	// Any fields in the request message which are not bound by the path
	// pattern automatically become (optional) HTTP query
	// parameters. Assume the following definition of the request message:

. The query parameters are implicitly bound to any variables not specified in the path. What you're looking for is

get: /dyeing/appid/{appid}/id_type/{id_type}

That should allow

GET /dyeing/appid/{appid}/id_type/{id_type}?page_num={page_num}&page_size={page_size}

To work.