The map_remote option lets you specify an arbitrary number of patterns thatĭefine replacements within HTTP request URLs before they are sent to a server. Served File: Preferred: ~/static-dir/ aboutusįallback: ~/static-dir/ aboutus/index.html HTTP Request URL: /index.php?page= aboutus │ Map_local option: |~m GET| /index.php\?page= (.+)| ~/static-dir │ │ In this example, all GET requests forĮ/index.php?page= are mapped to ~/static-dir/: If the file depends on the query string, we can use regex capturing groups. Served File: Preferred: ~/static-css /print/main.cssįallback: ~/static-css /print/main.css/index.html HTTP Request URL: /css /print/main.css ?timestamp=123 │ ▼ To illustrate this, consider the following example which maps all requests for /css* to the local directory ~/static-css. Directory traversal outside of the originally specified directory is not possible. If the file cannot be found, /index.html is appended and we try again. However, if url-regex contains a regex capturing group, this behavior changes and the first capturing group is appended instead (and query strings are not stripped). If local-path is a directory, url-regex is used to split the request URL in two parts and part on the right is appended to local-path, excluding the query string. File changes will be reflected immediately, there is no caching. If local-path is a file, this file will always be served. Replace /static/foo/bar.css with ~/static/foo/bar.css (but only for GET requests). Replace /static/foo/bar.css with ~/static/bar.css.

Replace /static/foo/bar.css with ~/static/foo/bar.css. The separator is arbitrary, and is defined by the first character ( | in the example above). That additionally constrains which requests will be redirected. It must match for a redirect to take place.įlow-filter is an optional mitmproxy filter expression Url-regex is a regular expression applied on the request URL. Local-path is the file or directory that should be served to the client. Map_local patterns look like this: |url-regex|local-path

The local file is fetched instead of the original resourceĪnd transparently returned to the client. The map_local option lets you specify an arbitrary number of patterns thatĭefine redirections of HTTP requests to local files or directories. Option, to make sure the server responds with complete data. You may want to use client-side replay in conjunction with the anticache This might differ from the recordedĬonversation, where requests may have been made concurrently. That mitmproxy serialises the requests, waiting for a response from the serverīefore starting the next request. HTTP conversation, and mitmproxy replays the client requests one by one. Note that this is not secure against an active adversary and can be bypassed, for example by switching to non-HTTP protocols.Ĭlient-side replay does what it says on the tin: you provide a previously saved # Examples Patternīlock all requests to, and return a “404 Not Found” instead.īlock all requests to, and do not send an HTTP response. The separator is arbitrary, and is defined by the first character. Served by mitmproxy for blocked requests.Ī special status code of 444 instructs mitmproxy to “hang up” and not send any response at all. That describes which requests should be blocked. flow-filter is an optional mitmproxy filter expression.Mitmproxy returns a fixed HTTP status code instead, or no response at all.īlock_list patterns look like this: /flow-filter/status-code Using the block_list option, you can block particular websites or requests. To make sure the server responds with complete data. It’s also often used during client-side replay, when you want This is useful when you want to make sure you capture an HTTP exchange If-modified-since) that might elicit a 304 Not Modified response from the When the anticache option is set, it removes headers ( if-none-match and

Mitmproxy examples