Ask HN: REST Custom Method: vs. /

Please help me understand why we would want to do this. At work, we've adopted this guide to specify an action on a resource:

https://cloud.google.com/apis/design/custom_methods

Instead of /api/job/:foo/cancel, they use /api/job/:foo:cancel.

I imagine URL parsers and routers have a much easier time with the former compared to the later. In the later, I imagine most people are having to do additional tokenizing to enable further routing. I can't think of a redeeming factor.

Thanks