Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Items explicitly excluded from the scope still saved in Proxy history

Julian | Last updated: Apr 16, 2020 06:38AM UTC

Version: Burp Professional v2020.2.1 Issue description: while having the out of scope Proxy history logging disabled, with the scope defined as follows (the IP address was changed): In scope: Enabled: yes Protocol: HTTPS Host/IP range: ^1\.2\.3\.4$ Port: ^443$ File: ^/.* Exclude from scope: Enabled: yes Protocol: HTTPS Host/IP range: ^1\.2\.3\.4$ Port: ^443$ File: ^/directory/subdirectory/.* So, Proxy and Target keep logging responses to all the requests directed at /directory/subdirectory/, which is exactly what I HAVE to avoid (I already know what those responses are, but the problem is they are VERY large, so my RAM runs out in a matter of minutes and I lose all my work). I still need to map the application and the only solution to this right now is to switch to something else, e.g. Squid.

Hannah, PortSwigger Agent | Last updated: Apr 16, 2020 12:19PM UTC

Have you tried enabling the "Drop all out-of-scope requests" feature? You can find this in "Project options > Connections > Out-of-scope requests".

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.