Rule's action execution is not correct?

Fiddler Everywhere Feedback Portal

Create an account Log In

Request a Feature Report a Bug

Unplanned

Last Updated: 19 Apr 2023 10:59 by ADMIN

I3eyonder

Created on: 15 Apr 2023 16:48

Type: Bug Report

Rule's action execution is not correct?

I have 3 rules. Please check the images for detail how the rules define and their order of execution.

If I understand correctly, "Non-Final-After" rule must not be executed in this case due to "Final" rule contain a final action (Manual response).

But you can see, "non-final-after" header is added to response.

I am not sure if it's a bug or intended behavior.

Please take a look. Thanks.

Attached Files:

3 comments

ADMIN

Nick Iliev

Posted on: 19 Apr 2023 10:59

Hey Hieu Pham,

After additional investigation, I can confirm that the cases you have described are acting differently, which we can consider a bug. Thanks a lot for your time and detailed instructions to demonstrate your point. Currently, the team is researching the best approach to improve the final/non-final behavior so that we have a stable and predictable output, so your feedback is really valuable.

I will let you know as soon as we make a final decision on how we will approach the issue. Meanwhile, please do not hesitate to send us any feedback or ideas that you have related to the Rules and the Fiddler Everywhere application as a whole!

Regards,
Nick Iliev
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

I3eyonder

Posted on: 19 Apr 2023 02:12

So I might see some confused here. Let's take another example, please check the attachments.

For the case of "No Header Modified", you can see that there is no "non-final-after" custom response header at all.
I do the test for "Header Modified" case. If we made some modified to response before final action, maybe from another rule with higher priority like original post, or maybe from the rule that contained final action itself (as long as that action occur before final action). Then the rule that modify response header like "Non-Final After Final Rule" will be executed.

Thanks.

Attached Files:

ADMIN

Nick Iliev

Posted on: 18 Apr 2023 12:41

Hello Hieu,

Indeed, at this very moment (version 4.2.0 of Fiddler Everywhere), the behavior of the final actions changed, and as we speak, the latest version of Fiddler Everywhere works as follows:

- A Final action effectively blocks all final actions from any other active rule.

- The actions are executed by order of their appearance in the rule, which means that if there are multiple final actions, only the topmost will be executed.

- The rules are executed by order of their appearance in the Rules Queue. A rule that contains a final action won't block rules with lower priority but will block any other final action contained in these rules.

- Non-final actions always execute and won't be blocked from a final action.

The final actions in Fiddler Everywhere are Manual Presponse, Predefined Response, Response File, Magic String, Graceful Close, Non-Graceful Close, Do Not Show, and Do Not Decrypt.

That said, the team is currently discussing if it would make sense for a final action to directly block all other actions (similar to how things were working in Fiddler Classic and its AutoResponder) or if we should really only stop other final actions and allow non-final actions and other rules (that contain non-final actions) to be executed. We are hearing different opinions and receiving additional feedback, so I can not clarify our final decision yet. Still, I will post it here as soon as a concrete decision is made.

Regards,
Nick Iliev
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.