You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I just spent quite a bit of time debugging why Reshaper would not work in the Repeater tool, even with the Repeater tool enabled in the Reshaper settings. In the logs I could see that the rules were triggering and executing properly, but their output was not reflected in the Repeater response pane.
I found that if the popular extension Logger++ is loaded, and Logger++ is found below Reshaper in the load order, Reshaper will not be able to modify the Repeater response pane.
Example rule:
I'm not sure how to fix this, I think its a regression in Burp because I always have Logger++ as the very last extension in the load order. Might be something to document in the extension?
The text was updated successfully, but these errors were encountered:
Hi @ldionmarcil ,
Thanks for the nice write-up. This issue is not expected functionality. The same issue has been reported by users of Logger++ in combo with other extensions in the Portswigger Discord as well. See https://discord.com/channels/1159124119074381945/1164175825474686996/1315709434261147721. Current speculation by the Logger++ dev is that it is a Burp Suite bug as you've mentioned. I'm keeping an eye on the situation.
Hi, I just spent quite a bit of time debugging why Reshaper would not work in the Repeater tool, even with the Repeater tool enabled in the Reshaper settings. In the logs I could see that the rules were triggering and executing properly, but their output was not reflected in the Repeater response pane.
I found that if the popular extension Logger++ is loaded, and Logger++ is found below Reshaper in the load order, Reshaper will not be able to modify the Repeater response pane.
Example rule:
JSON export
Scenario 1
Load order
Repeater
Scenario 2
Load order
Repeater
I'm not sure how to fix this, I think its a regression in Burp because I always have Logger++ as the very last extension in the load order. Might be something to document in the extension?
The text was updated successfully, but these errors were encountered: