Values containing slashes in URL template? about grpc-gateway

[dmitshur]

Confirmed that it works. It's possible to achieve the above by doing:

get: "/v1/dirs/{dir_path=**}"

[dmitshur]

I just realized (thanks @sqs) that I missed a very important bit:

* matches a single path component, ** zero or more path components.

So it is possible.

[slimsag]

@shurcooL Do I understand your findings here correctly?

get: "/v1/dirs/{dir_path}"

Would match only a single path element (but it could be a URI encoded path). Whereas:

get: "/v1/dirs/{dir_path=**}"

Would match multiple path elements (that are not URI encoded)?

[dmitshur]

@slimsag Yes, the above is correct.

(but it could be a URI encoded path)

I don't think so. This is a url path element, not a query parameter. Edit: I could be mistaken, see e.g., golang/go#5777 (comment).

---

However, I'm reopening this because I find that it only works if such segment is at the end of the route. It doesn't seem to work when it's in the middle.

For example, this works:

get: "/v1/dirs/{dir_path=**}"

// They all work.
/v1/dirs/foo
/v1/dirs/foo/bar
/v1/dirs/foo/bar/baz

But this does not work:

get: "/v1/dirs/{dir_path=**}/.files"

// None of these get matched.
/v1/dirs/foo/.files
/v1/dirs/foo/bar/.files
/v1/dirs/foo/bar/baz/.files

Is that a bug?

[yugui]

@shurcooL Your question is whether the multi-segment wildcard ** is greedy or not.
I believe it is and I implemented the match mechanism as greedy by intention. But it is not clearly described in the spec.
We might need to ask the spec owner.

[dmitshur]

Your question is whether the multi-segment wildcard ** is greedy or not.

That is true. I agree that the spec doesn't seem to specify one way or the other. Thanks for looking into it.

[dmitshur]

Thank you for resolving this!