I have an MPGW with a dynamic backend that must process GET and POST requests. The problem is I cannot set the backend in a request rule when a GET is received - due to "The one way exchange pattern will bypass the execution of the selected request rule" (from the log). Come to think of it, I can't do anything useful with a GET request in MPGW if I can't invoke a request rule - so GET might as well be crippled :(
My question is: is there a way to enable request rule processing in MPGW given a HTTP GET request? I can't find a HTTP handler of MPGW setting to enable it, but perhaps I missed it or there is another workaround?
This topic has been locked.
Pinned topic MPGW - how to make a HTTP GET process a request rule?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
swlinn 100000E7QE1445 Posts
Re: MPGW - how to make a HTTP GET process a request rule?2010-02-22T14:35:41ZThis is the accepted answer. This is the accepted answer.On your FSH, do you have the GET method enabled? Also, GET methods are by their nature, non-XML. If you are not doing a HTTP Convert operation as the first operation of your request rule, then try to enable non-XML processing in the rule (accessible from the processing rule link from the objects menu).
dp-dude 270002J6CC19 Posts
Re: MPGW - how to make a HTTP GET process a request rule?2010-02-22T16:11:20ZThis is the accepted answer. This is the accepted answer.
- swlinn 100000E7QE
NB: I really can't fathom why so many options have to be "hidden" under the Objects menu like this. Why can't I just edit this property from the MPGW Policy/Rule editing page like everything else? Oh well, I guess the moral of the story is to always go digging under the Object menue when trying to find the hidden option...
SystemAdmin 110000D4XK6772 Posts
Re: MPGW - how to make a HTTP GET process a request rule?2010-03-08T16:50:23ZThis is the accepted answer. This is the accepted answer.I got into same problem. I enabled GET with my FSH and set Non-xml processing with my request rule. MPG has strted picking up my request rule but I have a transform action in my requset rule which is used to dynamically select a routing URL.
I'm getting error while executing the transform action.
local://Request.xsl:7: type of the right-hand side of / operator must be a nodeset, but isn't
How can I execute a xsl when request rule is running for http get request.
SystemAdmin 110000D4XK6772 Posts
Re: MPGW - how to make a HTTP GET process a request rule?2010-03-08T17:35:33ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
1) Set the Input Context of transform action that runs Request.xsl to NULL. This assumes that you have no need to look inside the payload when making your routing decision.
2) Use a match rule to pickup HTTP GET calls and set up the processing on the rule appropriately. Use HTTP-Convert as the first action on the rule, which'll convert the call to XML, and then use the transform action that runs Request.xsl.
BillHines 1000009APS76 Posts
Re: MPGW - how to make a HTTP GET process a request rule?2010-03-09T20:10:26ZThis is the accepted answer. This is the accepted answer.
- dp-dude 270002J6CC
Author of IBM WebSphere DataPower SOA Appliance Handbook published by IBM Press (with John Rasmussen, Jaime Ryan, Simon Kapadia, Jim Brennan)
maduriDP 270002NRDJ39 Posts
Re: MPGW - how to make a HTTP GET process a request rule?2010-10-25T15:34:34ZThis is the accepted answer. This is the accepted answer.I am still facing the same problem -
1. Checked Non-XML processing to On
2. Turned "Process empty messages" to On
3. My Match Action is of Type URL with /a/b/c
4. However when I send a request with URI /a/b/d , I expect the request to not go through , However the request succeeds.
5. This is what I get in the system logs -
"xmlfirewall (XMLFW-CFS-DPHealth): The one way exchange pattern will bypass the execution of the selected rule
xmlfirewall (XMLFW-CFS-DPHealth): No match from processing policy 'XMLFW-CFS-DPHealth' - default rule selected.
Matching (XMLFW-CFS-DPHealth): No match: Received URL [/a/b/d/] does not match rule '/a/b/c'
We are clueless... Any help would be greatly appreciated!!!
HermannSW 2700006U548691 Posts