Misc User Options
These settings let you configure hotkeys for common actions. Numerous types of actions can be assigned a hotkey, in the following categories:
- Actions specific to an individual HTTP request or response, such as "Send to Repeater".
- Global actions, such as "Switch to Proxy".
- In-editor actions, such as "Cut" and "Undo".
A number of hotkeys are configured by default. Note that very many more actions are available to have a hotkey assigned, if you use them frequently.
All hotkeys must use the Control key (or the Command key on OSX), and may also use Shift and other available modifiers. Note that on some Windows installations the Ctrl+Alt combination is treated by Windows as equivalent to AltGr, and so may result in typed characters appearing when pressed in text fields.
This option lets you configure whether Proxy interception should be enabled when Burp is started up. You can choose to always enable interception, always disable interception, or to restore the setting from when Burp was last closed.
Proxy History Logging
This option controls whether adding items to Target scope will automatically set the Proxy option to stop sending out-of-scope items to the history or other Burp tools. Setting Burp to do this is useful to avoid accumulating project data for out-of-scope items.
Temporary Files Location
These settings let you configure where Burp stores its temporary files.
By default, Burp creates a directory within the temporary file location provided by the platform. You can modify this behavior to use a custom directory - for example, on a different volume, or which is not world-readable.
On Mac OS X, you may find that the default temporary file location is sometimes cleared following system hibernation, causing Burp to lose its temporary files. You can resolve this problem by configuring a custom location for Burp to store its temporary files.
Changes to this setting take effect the next time Burp starts up.
You can help improve Burp by submitting anonymous feedback about Burp's performance.
Feedback only contains technical information about Burp's internal functioning, and does not identify you in any way. If you do report a bug, you can help us diagnose any problems that your instance of Burp has encountered by including your debug ID.