You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/05/06 13:31:38 UTC
[GitHub] csantanapr commented on issue #3593: Include API GW path parameters
as event parameters.
csantanapr commented on issue #3593: Include API GW path parameters as event parameters.
URL: https://github.com/apache/incubator-openwhisk/issues/3593#issuecomment-386879644
@ddragosd
Yes they are already in mapped today in swagger config for the operation
The problems I see for using query is conflicting with actual query parameters.
?name=Carlos
The user doesn’t know if name is referring to a query, or path param
In cases where /api/:name/profile?name=
If we really want to use query we need to namespace them with something like _ow
Then gateway would send to the web action /api/Alberto/profile?name=Carlos&_ow_path_name=Alberto
With this then no controller changes and user get all path parameters from query parameters that start with some prefix _ow_path_*
Is this what your were proposing?
Again like I said an issue to be discuss on what’s best for apigateway to implement t
Send path parameters via a header or custom query parameters
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services