apigeetool base path param problem

Not applicable

I found an issue with apigeetool for a regular proxy deploy. when i use the -b param and specify a value like "/v1/demo_proxy" the /v1 gets stripped out!

Is there a way to override this or make it work?

0 2 207
2 REPLIES 2

Hi @Benjamin Goldman --

After trying this myself, I found that when I used -b with apigeetool, the base path does not show up in the UI or in the proxy files themselves (making it look like it was stripped off). However, when I call the proxy with the specified base path, it works!

So, if I specified -b /v1/demo and deploy. Then call the api like this, it fails:

curl -i http://docs-prod.apigee.net/xmltojson/forecastrss?w=12797282

But, like this, it succeeds (as expected):

curl -i http://docs-prod.apigee.net/v1/demo/xmltojson/forecastrss?w=12797282

But nowhere in the UI or the proxy files can I see that the base path is /v1/demo. I'm trying to find out why, and filed a bug to try to get this fixed if it's a bug (or at least a correct explanation of how things are supposed to work work). I'll respond when I find out more.

Thanks,

Will

I just ran into something similar. Any update?

The other thing that I found is that, even when I specify my base-path as /v2, it gets deployed as /v2/<original-base-path>. Shouldn't I be able to replace the base-path, rather than just adding to it?