Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bambda does not auto-refresh inscope only #88

Closed
kirs112 opened this issue Feb 6, 2025 · 5 comments
Closed

bambda does not auto-refresh inscope only #88

kirs112 opened this issue Feb 6, 2025 · 5 comments

Comments

@kirs112
Copy link

kirs112 commented Feb 6, 2025

Hi !
I found that setting scope only when using bambda does not automatically refresh the history.

@Hannah-PortSwigger
Copy link
Contributor

Hi

Could you provide some more information on the behavior you are experiencing, please?

If you have an example Bambda, that may be helpful to include.

@kirs112
Copy link
Author

kirs112 commented Feb 6, 2025

Hi @Hannah-PortSwigger

After updating the scope, it is always necessary to manually update the bambda expression to refresh the history

var inScopeOnly = false;

if (inScopeOnly) {
return requestResponse.request().isInScope();
}

return true;

@kirs112
Copy link
Author

kirs112 commented Feb 6, 2025

Here's a link to the video I recorded, which I can't upload here due to github size limitations

https://drive.google.com/file/d/1YjJFL5oo_IOmR-0hWWRLB8AA_jLBbAyx/view?usp=sharing

@Hannah-PortSwigger
Copy link
Contributor

Thanks for the description and the video!

I've tested this with a simple return requestResponse.request().isInScope();, and when changing my "Target > Scope", the entries in my Proxy History table do automatically get re-filtered with the new scope applied.

Could you check this and confirm that you see the same behavior?

@kirs112
Copy link
Author

kirs112 commented Feb 9, 2025

HI @Hannah-PortSwigger

Sorry it's probably my other bambda expressions that are interfering with the run, I can't reproduce it at the moment

@kirs112 kirs112 closed this as completed Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants