Extensions settings

The Extensions page in the Settings dialog contains settings for the following:

• Startup behavior.
• Java environment.
• Python environment.
• Ruby environment.

Startup behavior

These settings determine how Burp Suite handles extensions on startup:

• Automatically reload extensions on startup - Enable this setting to reload all extensions when you restart Burp. Note that even with this setting enabled, you can restart Burp without reloading extensions. Launch Burp from the command line, and use the --disable-extensions command line flag.
• Automatically update installed BApps on startup - If you enable this setting, Burp automatically checks for updates to your installed extensions in the BApp Store.

Java environment

This setting enables you to specify a folder from which Burp can load Java libraries. Burp searches the specified folder and any subfolders for JAR files. It includes them in the classpath of the classloader that loads Java extensions.

Python environment

These settings enable you to configure the environment in which Python-based extensions are executed:

• Location of the Jython standalone JAR file - Specify the location of a Jython standalone JAR file. When loaded, it shows the file location. Jython is a Python interpreter that runs on the Java platform. It enables extensions written in Python to interact with Burp's legacy Java-based Extender API.
• Folder for loading modules - Specify the location of a folder containing Python modules. Burp updates the Python sys.path variable with the specified location. This is useful if you create your own set of Python modules for use with multiple separate extensions.

Ruby environment

This setting enables you to specify the location of JRuby standalone JAR file. When loaded, it shows the file location.

JRuby is a Ruby interpreter that runs on the Java platform. It enables extensions written in Ruby to interact with Burp's legacy Java-based Extender API.