A rule for avoiding socket.io noise?
Hi dear portswigger community... could you recommend any rule / way in order to avoid intercepting all the data being sent over sockets?
There's a video streaming in the background, and I'm trying to capture and work with a limited set of parameters, but the amount of data makes it hard to properly intercept...
Hi Chris, Unfortunately, this is not configurable in Burp Suite, in theory, it might be possible by chaining multiple Burp Suite instances together and using Match & Replace rules to identify the unwanted communication but it would be difficult to set up so it’s not advisable.
If this is of interest to you would you like me to create a feature request?