Add http proxy cababitlity for rest-trigger #150
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pass Through Proxy
The idea is to have the REST Trigger and REST activity (https://github.com/project-flogo/contrib/tree/master/activity/rest)
changed in such away, that there is a possiblity to create a flogo app that has pass through proxy functionalities.
CHANGES TRIGGER:
Handle the existing functionality of create a path variable of the last part of the url coming in of the trigger (github.com/julienschmidt/httprouter):
example: incoming url: http://tibco.org/path/that/comes/in definition in trigger: /:restOfPath will
define a pathParams key: 'restOfPath' value: 'path/that/comes/in'
This :restOfPath definition in the trigger will also be exposed to the outside world e.g. mashery.
In mashery there is no option to change this mapping, therefore the trigger needs to be changed to automatically
create the 'restOfPath' variable for the rest of the path as defined in the trigger.
It will do so, using a boolean 'isPassThrough' to be able to turn this functionality on/off