Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 3.3 M2
-
Component/s: Core: Routing / Filters
-
Labels:None
-
User impact:High
-
Effort points:3
-
Affects Docs:Yes
-
Similar Issues:None
-
Effort:S
-
% Users Impacted:>80%
-
Value:5
Description
This is meant as a high level issue to capture the overall story and track sub issues
Story: as a user, I want to use Mule to act as a proxy between clients and my REST services. This proxy should be able to route based on custom logic, propagate HTTP headers, propagate HTTP paths, etc. There are 3 actors in this story:
client <> proxyhost <> desetination
For example, I want to get a request to http://proxyhost/restrouter/myservice/param1/param2?queryparam1=foo1&queryparam2=foo2. I want to be able to route based on the service name, then propogate portions of that URL to my destination service. For example: http://destination/basepath/param1/param2?queryparam1=foo1&queryparam2=foo2. This request could have custom application HTTP headers as well which need to be automatically propagated.