Getting Started with Burp Suite
Burp Suite Documentation
Take a look at our Documentation section for full details about every Burp Suite tool, function and configuration option.
| Burp Suite Professional and Community editions | Burp Suite Enterprise Edition |
| Burp Scanner | Burp Collaborator |
| Burp Infiltrator | Full Documentation Contents |
Burp Extender
Burp Extender lets you extend the functionality of Burp Suite in numerous ways.
Extensions can be written in Java, Python or Ruby.
| API documentation | Writing your first Burp Suite extension |
| Sample extensions | View community discussions about Extensibility |
HTTP History and patterns
Hi, Is there any mean to avoid a request with a pattern to be sent to HTTP history?
I mean, being someone that deals a lot with HTTP history I want sometimes to avoid my HTTP history to be polluted with analytics paths such as `POST /tracking/logging`, how do I avoid Burp sending those requests to HTTP history?
I tried intercepting that request then right-click, "Don't intercept requests" > "For this directory" but it does not seem to work. am I missing something?
Have you tried setting your scope and then use check the box next to “Don’t send items to Proxy history or live tasks, if out of scope” in the Proxy > Options > Misc tab?
- https://portswigger.net/burp/documentation/desktop/tools/proxy/options#miscellaneous