Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request full url path in function context #1153

GIG0i opened this issue Apr 8, 2019 · 1 comment · Fixed by #1266


Copy link

commented Apr 8, 2019

It would be very useful if from within the function we could retrieve the request full url path so that a single function, with a single deployment, can be used for multiple routes. This would still require some logic on the application side to map url paths to specific entry points/controllers.

Currently, for example using the Python environment (which comes pre-loaded with Flask), I haven't found any way to retrieve the request full url path. The Flask request object will return only the base domain and there are no headers that expose the full path.


  • I know that the current guideline is to create a new function (using the same codebase) for each route so that different entry points can be configured.
  • Currently it is possible to retrieve the url params, but not the full url path:

This comment has been minimized.

Copy link

commented May 1, 2019

Yeah this is a reasonable thing to add as a header, shouldn't be too difficult.

@soamvasani soamvasani added this to the 1.3 milestone May 1, 2019

@life1347 life1347 assigned darkgerm and unassigned soamvasani May 23, 2019

@vishal-biyani vishal-biyani modified the milestones: 1.3, 1.4 May 30, 2019

@vishal-biyani vishal-biyani modified the milestones: 1.4, 1.5 Jul 4, 2019

@life1347 life1347 assigned life1347 and unassigned darkgerm Aug 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
5 participants
You can’t perform that action at this time.