Selenium Wire extends Selenium's Python bindings to give your tests access to the underlying requests made by the browser. It is a lightweight library designed for ease of use with minimal external dependencies.
With Selenium Wire, you author your tests in just the same way as you do with Selenium, but you get an additional user-friendly API for accessing things such as the request/response headers, status code and body content.
from seleniumwire import webdriver # Import from seleniumwire
# Create a new instance of the Firefox driver
driver = webdriver.Firefox()
# Go to the Google home page
driver.get('https://www.google.com')
# Access requests via the `requests` attribute
for request in driver.requests:
if request.response:
print(
request.url,
request.response.status_code,
request.response.headers['Content-Type']
)
Prints:
https://www.google.com/ 200 text/html; charset=UTF-8
https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_120x44dp.png 200 image/png
https://consent.google.com/status?continue=https://www.google.com&pc=s×tamp=1531511954&gl=GB 204 text/html; charset=utf-8
https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_272x92dp.png 200 image/png
https://ssl.gstatic.com/gb/images/i2_2ec824b0.png 200 image/png
https://www.google.com/gen_204?s=webaft&t=aft&atyp=csi&ei=kgRJW7DBONKTlwTK77wQ&rt=wsrt.366,aft.58,prt.58 204 text/html; charset=UTF-8
...
- Pure Python, user-friendly API
- HTTP and HTTPS requests captured
- Access headers, parameters, body
- Modify headers, parameters
- Rewrite URLs
- Proxy server support
- Python 3.4+
- Selenium 3.4.0+
- Firefox, Chrome, Safari and Edge are supported
- Installation
- Usage
- Request Attributes
- Response Attributes
- Modifying Requests and Responses
- Proxies
- Backends
- Certificates
- All Options
- Limitations
- License
Install using pip:
pip install selenium-wire
Selenium Wire requires OpenSSL for capturing HTTPS requests.
Linux
# For apt based Linux systems
sudo apt install openssl
# For RPM based Linux systems
sudo yum install openssl
MacOS
brew install openssl
Windows
No installation is required - OpenSSL for Windows is bundled with Selenium Wire.
Firefox and Chrome
No specific configuration should be necessary - everything should just work.
You will however need to ensure that you have downloaded the Gecko driver and Chrome driver for Firefox and Chrome to be remotely controlled - the same as if you were using Selenium directly. Once downloaded, these executables should be placed somewhere on your PATH.
Safari
There are a few manual steps that have to be carried out before you can use Safari with Selenium Wire.
Edge
Like Safari, Microsoft Edge requires some manual configuration before it can be used with Selenium Wire.
Ensure that you import webdriver
from the seleniumwire
package:
from seleniumwire import webdriver
- For sub-packages of
webdriver
, you should continue to import these directly fromselenium
. For example, to importWebDriverWait
:
# Sub-packages of webdriver must still be imported from `selenium` itself
from selenium.webdriver.support.ui import WebDriverWait
For Firefox and Chrome, you don't need to do anything special. Just instantiate the webdriver as you would normally, passing in Selenium specific options if you have any. Selenium Wire also has it's own options that can be passed in the seleniumwire_options
attribute.
Firefox
driver = webdriver.Firefox()
Chrome
driver = webdriver.Chrome()
Safari
For Safari, you need to tell Selenium Wire the port number you selected when you configured the browser in Browser Setup.
For example, if you chose port 12345, then you would pass it in the seleniumwire_options
like this:
driver = webdriver.Safari(seleniumwire_options={'port': 12345})
Edge
For Edge, you need to tell Selenium Wire the port number you selected when you configured the browser in Browser Setup.
For example, if you chose port 12345, then you would pass it in the seleniumwire_options
like this:
driver = webdriver.Edge(seleniumwire_options={'port': 12345})
Selenium Wire captures all HTTP/HTTPS traffic made by the browser during a test.
driver.requests
You can retrieve all requests with the driver.requests
attribute. The requests are just a list and can be iterated (like in the opening example) and indexed:
first_request = driver.requests[0]
driver.last_request
The list of requests held by driver.requests
is in chronological order. If you want to access the most recent request, use the dedicated driver.last_request
attribute:
last_request = driver.last_request
This is more efficient than using driver.requests[-1]
.
When you ask for captured requests using driver.requests
or driver.last_request
you have to be sure that the requests you're interested in have actually been captured. If you ask too soon, then you may find that a request is not yet present, or is present but has no associated response.
driver.wait_for_request(path)
This method will wait for a previous request with a specific URL to complete before allowing the test to continue. The path
attribute can be a regex that will be searched within the request URL.
For example, to wait for an AJAX request to return after a button is clicked:
# Click a button that triggers a background request to https://server/api/products/12345/
button_element.click()
# Wait for the request/response to complete
request = driver.wait_for_request('/api/products/12345/$')
- Note that
driver.wait_for_request()
doesn't make a request, it just waits for a previous request made by some other action. - Note that because the
path
can be a regex, you must escape special characters such as question marks with a slash.
The wait_for_request()
method will return the first fully completed request it finds that matches the supplied path. Fully completed meaning that the response must have returned. The method will wait up to 10 seconds by default but you can vary that with the timeout
argument:
# Wait up to 30 seconds for a request/response
request = driver.wait_for_request('/api/products/12345/$', timeout=30)
If a fully completed request is not seen within the timeout period a TimeoutException
is raised.
To clear previously captured requests, use del
:
del driver.requests
By default, Selenium Wire will capture all requests the browser makes during a test. You may want to restrict this to particular URLs - e.g. for performance reasons.
To restrict request capture use the scopes
attribute. This accepts a list of regular expressions that will match URLs to be captured.
driver.scopes = [
'.*stackoverflow.*',
'.*github.*'
]
# Only request URLs containing "stackoverflow" or "github" will now be captured...
Requests have the following attributes.
method
- The HTTP method type, e.g.
GET
orPOST
. url
- The request URL, e.g.
https://server/some/path/index.html?foo=bar&spam=eggs
path
- The request path, e.g.
/some/path/index.html
querystring
- The query string, e.g.
foo=bar&spam=eggs
params
- A dictionary of request parameters. If a parameter with the same name appears more than once in the request, it's value in the dictionary will be a list.
headers
- A case-insensitive dictionary of request headers. Asking for
request.headers['user-agent']
will return the value of theUser-Agent
header. body
- The request body as
bytes
. If the request has no body the value ofbody
will be empty, i.e.b''
. response
- The response associated with the request. This will be
None
if the request has no response.
The response can be retrieved from a request via the response
attribute. A response may be None
if it was never captured, which may happen if you asked for it before it returned or if the server timed out etc. A response has the following attributes.
status_code
- The status code of the response, e.g.
200
or404
. reason
- The reason phrase, e.g.
OK
orNot Found
. headers
- A case-insensitive dictionary of response headers. Asking for
response.headers['content-length']
will return the value of theContent-Length
header. body
- The response body as
bytes
. If the response has no body the value ofbody
will be empty, i.e.b''
. If the body was compressed (zipped) by the server it will automatically be uncompressed.
Selenium Wire allows you to modify requests and responses. Requests are modified after the browser sends them and responses are modified before the browser receives them.
The driver.header_overrides
attribute is used for modifying headers.
To add one or more new headers to a request, create a dictionary containing those headers and set it as the value of header_overrides
.
driver.header_overrides = {
'New-Header1': 'Some Value',
'New-Header2': 'Some Value'
}
# All subsequent requests will now contain New-Header1 and New-Header2
If a header already exists in a request it will be overwritten by the one in the dictionary. Header names are case-insensitive.
For response headers, just prefix the header name with response:
driver.header_overrides = {
'New-Header1': 'Some Value',
'response:New-Header2': 'Some Value'
}
# All subsequent requests will now contain New-Header1
# All responses will contain New-Header2
To remove one or more headers from a request or response, set the value of those headers to None
.
driver.header_overrides = {
'Existing-Header1': None,
'response:Existing-Header2': None
}
# All subsequent requests will *not* contain Existing-Header1
# All responses will *not* contain Existing-Header2
Header overrides can also be applied on a per-URL basis using a regex to match the appropriate request URL:
driver.header_overrides = [
('.*prod1.server.com.*', {'User-Agent': 'Test_User_Agent_String',
'response:New-Header': 'HeaderValue'}),
('.*prod2.server.com.*', {'User-Agent': 'Test_User_Agent_String2',
'response:New-Header': 'HeaderValue2'})
]
# Only requests/responses to prod1.server.com or prod2.server.com will have their headers modified
To clear the header overrides that you have set, use del
:
del driver.header_overrides
The driver.param_overrides
attribute is used for modifying request parameters. Parameters are modified after the browser sends them.
For GET requests the query string is modified. For POST requests that have a content type of application/x-www-form-urlencoded
the body of the request is modified.
To add one or more new parameters to a request, create a dictionary containing those parameters and set it as the value of param_overrides
.
driver.param_overrides = {
'new_param1': 'val1',
'new_param2': 'val2'
}
# All subsequent requests will now contain new_param1 and new_param2
If a parameter already exists in a request it will be overwritten by the one in the dictionary.
To remove one or more parameters from a request, set the value of those parameters to None
.
driver.param_overrides = {
'existing_param1': None,
'existing_param2': None
}
# All subsequent requests will *not* contain existing_param1 or existing_param2
Perhaps more usefully, parameter overrides can be applied on a per-URL basis using a regex to match the appropriate request URL:
driver.param_overrides = [
('https://server/some/path.*', {'new_param1': 'val1',
'new_param2': 'val2'}),
('https://server/some/other/path.*', {'new_param3': 'val3'})
]
# Only requests starting https://server/some/path and https://server/some/other/path
# will have their parameters modified
To clear the parameter overrides that you have set, use del
:
del driver.param_overrides
The driver.querystring_overrides
attribute is used for modifying the whole request query string. The query string is modified after the browser sends the request.
Specifying a query string override will replace any existing query string in the request, or will add it to the request if it doesn't already exist.
driver.querystring_overrides = 'foo=bar&spam=eggs'
# All subsequent requests will now have the query string foo=bar&spam=eggs
# e.g. http://server/some/path?foo=bar&spam=eggs
To remove a query string from a request, set the value to empty string.
driver.querystring_overrides = ''
# All subsequent requests will *not* contain a query string
Perhaps more usefully, query string overrides can be applied on a per-URL basis using a regex to match the appropriate request URL:
driver.querystring_overrides = [
('https://server/some/path.*', 'foo=bar&spam=eggs'),
('https://server/some/other/path.*', 'a=b&c=d&x=z')
]
# Only requests starting https://server/some/path and https://server/some/other/path
# will have their query strings modified
To clear the query string overrides that you have set, use del
:
del driver.querystring_overrides
The driver.rewrite_rules
attribute is used for rewriting request URLs. URLs are rewritten after the browser sends the request.
Each rewrite rule should be specified as a 2-tuple or list, the first element containing the URL pattern to match and the second element the replacement. One or more rewrite rules can be supplied.
driver.rewrite_rules = [
(r'(https?://)prod1.server.com(.*)', r'\1prod2.server.com\2'),
]
# All subsequent requests that match http://prod1.server.com... or https://prod1.server.com...
# will be rewritten to http://prod2.server.com... or https://prod2.server.com...
The match and replacement syntax is just Python's regex syntax. See re.sub for more information.
To clear the rewrite rules that you have set, use del
:
del driver.rewrite_rules
If the site you are testing sits behind a proxy server you can tell Selenium Wire about that proxy server in the options you pass to the webdriver instance. The configuration takes the following format:
options = {
'proxy': {
'http': 'http://192.168.10.100:8888',
'https': 'https://192.168.10.100:8889',
'no_proxy': 'localhost,127.0.0.1'
}
}
driver = webdriver.Firefox(seleniumwire_options=options)
To use HTTP Basic Auth with your proxy, specify the username and password in the URL:
options = {
'proxy': {
'https': 'https://user:[email protected]:8889',
}
}
For proxy authentication different to Basic, you can supply the full value for the Proxy-Authorization
header using the custom_authorization
option. For example, if your proxy used the Bearer scheme:
options = {
'proxy': {
'https': 'https://192.168.10.100:8889', # No username or password used
'custom_authorization': 'Bearer mytoken123' # Custom Proxy-Authorization header value
}
}
Note that the custom_authorization
option is only supported by the default backend.
The proxy configuration can also be loaded through environment variables called HTTP_PROXY
, HTTPS_PROXY
and NO_PROXY
:
$ export HTTP_PROXY="http://192.168.10.100:8888"
$ export HTTPS_PROXY="https://192.168.10.100:8889"
$ export NO_PROXY="localhost,127.0.0.1"
Using a SOCKS proxy is the same as using an HTTP based one:
options = {
'proxy': {
'http': 'socks5://user:[email protected]:8888',
'https': 'socks5://user:[email protected]:8889',
'no_proxy': 'localhost,127.0.0.1'
}
}
driver = webdriver.Firefox(seleniumwire_options=options)
You can leave out the user
and pass
if your proxy doesn't require authentication.
As well as socks5
, the schemes socks4
and socks5h
are supported. Use socks5h
when you want DNS resolution to happen on the proxy server rather than on the client.
Using Selenium Wire with Tor
See this example if you want to run Selenium Wire with Tor.
Selenium Wire allows you to change the backend component that performs request capture. Currently two backends are supported: the backend that ships with Selenium Wire (the default) and the mitmproxy backend.
The default backend is adequate for most purposes. However, in certain cases you may find you get better performance with the mitmproxy backend.
The mitmproxy backend relies upon the powerful open source mitmproxy proxy server being installed in your environment.
To switch to the mitmproxy backend, first install the mitmproxy package:
pip install mitmproxy
Once installed, set the backend
option in Selenium Wire's options to mitmproxy
:
options = {
'backend': 'mitmproxy'
}
driver = webdriver.Firefox(seleniumwire_options=options)
Mitmproxy backend limitations
- You must be running Python 3.6 or higher.
- The mitmproxy backend won't work with upstream SOCKS proxies.
Selenium Wire uses it's own CA certificate to decrypt HTTPS traffic. It is not normally necessary for the browser to trust this certificate because Selenium Wire tells the browser to add it as an exception. This will allow the browser to function normally, but it will display a "Not Secure" message in the address bar. If you wish to get rid of this message you can install the CA certificate manually.
For the default backend, you can download the CA certificate here. Once downloaded, navigate to "Certificates" in your browser settings and import the certificate in the "Authorities" section.
If you are using the mitmproxy backend, you can follow these instructions to install the CA certificate.
A summary of all options that can be passed to Selenium Wire via the seleniumwire_options
webdriver attribute.
backend
- The backend component that Selenium Wire will use to capture requests. The currently supported values are
default
(same as not specifying) ormitmproxy
.
options = {
'backend': 'mitmproxy' # Use the mitmproxy backend (see limitations above)
}
driver = webdriver.Firefox(seleniumwire_options=options)
connection_keep_alive
- Whether connections should be reused across requests. The default is
False
. Applies to the default backend only.
options = {
'connection_keep_alive': True # Allow persistent connections
}
driver = webdriver.Firefox(seleniumwire_options=options)
connection_timeout
- The number of seconds Selenium Wire should wait before timing out requests. The default is 5 seconds. Increase this value if you're working with a slow server that needs more time to respond. Set to
None
for no timeout. Applies to the default backend only.
options = {
'connection_timeout': None # Never timeout
}
driver = webdriver.Firefox(seleniumwire_options=options)
custom_response_handler
- This function that should be passed in custom response handlers should maintain a signature that it compatible with
CaptureRequestHandler.handle_response
, as all arguments passed to that function will in turn be passed to your function. In order to modify the response data, you will need to return it from your function (the response data for the request is given in theres_body
argument). Applies to the default backend only.
def custom(req, req_body, res, res_body):
print(f'res_body length: {len(res_body)}')
options = {
'custom_response_handler': custom
}
drv = webdriver.Firefox(seleniumwire_options=options)
drv.get('https://example.com')
The code above will print something like this to the console (loading a page will almost always initiate more than one request):
res_body length: 471
res_body length: 606
disable_encoding
- Whether to disable content encoding. When set to
True
, theAccept-Encoding
header will be set toidentity
for all requests. This tells the server to not compress/modify the response. The default isFalse
.
options = {
'disable_encoding': True # Tell the server not to compress the response
}
driver = webdriver.Firefox(seleniumwire_options=options)
ignore_http_methods
- A list of HTTP methods (specified as uppercase strings) that should be ignored by Selenium Wire and not captured. The default is
['OPTIONS']
which ignores all OPTIONS requests. To capture all request methods, setignore_http_methods
to an empty list:
options = {
'ignore_http_methods': [] # Capture all requests, including OPTIONS requests
}
driver = webdriver.Firefox(seleniumwire_options=options)
max_threads
- The maximum allowed number threads that will be used to handle requests. The default is 9999. Applies to the default backend only.
options = {
'max_threads': 3 # Allow a maximum of 3 threads to handle requests.
}
driver = webdriver.Firefox(seleniumwire_options=options)
mitmproxy_log_level
- Set the log level that the mitmproxy backend will use. The default is
ERROR
. Applies to the mitmproxy backend only.
options = {
'mitmproxy_log_level': 'INFO' # Increase the log level to INFO for the mitmproxy backend
}
driver = webdriver.Firefox(seleniumwire_options=options)
mitmproxy_confdir
- The location of the mitmproxy configuration directory. The default is
~/.mitmproxy
. You might want to change this if you're running in an environment where you don't have access to the user's home folder. Applies to the mitmproxy backend only.
options = {
'mitmproxy_confdir': '/tmp/.mitmproxy' # Switch the location to /tmp
}
driver = webdriver.Firefox(seleniumwire_options=options)
port
- The port number that Selenium Wire's backend listens on. You don't normally need to specify a port as a random port number is chosen automatically.
options = {
'port': 9999 # Tell the backend to listen on port 9999 (not normally necessary to set this)
}
driver = webdriver.Firefox(seleniumwire_options=options)
proxy
- The upstream proxy server configuration (if you're using a proxy).
options = {
'proxy': {
'http': 'http://user:[email protected]:8888',
'https': 'https://user:[email protected]:8889',
'no_proxy': 'localhost,127.0.0.1'
}
}
driver = webdriver.Firefox(seleniumwire_options=options)
request_storage_base_dir
- Captured requests and responses are stored in the current user's home folder by default. You might want to change this if you're running in an environment where you don't have access to the user's home folder.
options = {
'request_storage_base_dir': '/tmp' # Use /tmp to store captured data
}
driver = webdriver.Firefox(seleniumwire_options=options)
suppress_connection_errors
- Whether to suppress connection related tracebacks. The default is
True
so that harmless errors that commonly occur at browser shutdown do not alarm users. When suppressed, the connection error message is logged at DEBUG level without a traceback. Set toFalse
to allow exception propagation and see full tracebacks. Applies to the default backend only.
options = {
'suppress_connection_errors': False # Show full tracebacks for any connection errors
}
driver = webdriver.Firefox(seleniumwire_options=options)
verify_ssl
- Whether SSL certificates should be verified. The default is
False
which prevents errors with self-signed certificates.
options = {
'verify_ssl': True # Verify SSL certificates but beware of errors with self-signed certificates
}
driver = webdriver.Firefox(seleniumwire_options=options)
- Selenium Wire will currently work with tests that run on the same machine as the browser. A distributed setup using Selenium Grid is not yet supported.
- Sites that use NTLM authentication (Windows authentication) cannot currently be tested with Selenium Wire. NTLM authentication is not supported.
MIT