Wildcard Problem (GIN). Restful is not possible

krakend / krakend-ce

KrakenD Community Edition: High-performance, stateless, declarative, API Gateway written in Go.

https://www.krakend.io

Apache License 2.0

1.98k stars 452 forks source link

Wildcard Problem (GIN). Restful is not possible #276

Closed fgparamio closed 3 years ago

fgparamio commented 3 years ago

I have the same problem indicated in this link. When RestFul apis with child resources are exposed there are always wildcard problems:

https://stackoverflow.com/questions/61225833/krakend-api-gateway-panic-in-new-path-conflicts-with-existing-wildcard-in-exist

This is the JSON file:

krakend.log

It forces us to change the version of the end-points that give conflicts: v1, v2, v3, etc ... but that is a problem because it does not match the urls when working locally

Juandavi1 commented 3 years ago

Hi, i've the same issue

MrSmoke commented 3 years ago

yeah we have the same issue too. We've had to just use un-restful routes for now. I know you can swap out gin for mux (except some things stop working) but there doesn't really seem to be any solid docs (and not knowing go makes it a bit harder).

See https://github.com/devopsfaith/krakend-ce/issues/136

Ideally there would be a krakend-ce mux docker image we could use which is supported

github-actions[bot] commented 2 years ago

This issue was marked as resolved a long time ago and now has been automatically locked as there has not been any recent activity after it. You can still open a new issue and reference this link.