Skip to main content

Requests autocomplete

Easily search and prefill rules with information of HTTP requests triggered in the current web page. If you don't like reading much, we have a nice video here.

Enable requests capture​

  1. Click on the search icon in the top bar. This will instruct the extension to start recording HTTP requests triggered within the current browser tab.
  2. In the browser tab, trigger the HTTP requests you want to autocomplete.
  3. Search for the request directly in the URL field.
  4. Select a request and all the fields will be autocompleted for you with the available request information.

Search for HTTP requests in a page​

  • Search by request URL, this can simply the best keyword that identifies that request you're trying to grab.
  • Search by HTTP method. If you search for GET, you will see all the GET requests available. Note: all the HTTP method keywords are case-sensitive. Sometimes it can be useful to search using the HTTP method if you have no clue how the request URL looks like, but you do know upfront its method.

Using regular expressions for searching​

Yes, if you turn on the regular expression toggle, you will be able to filter results with regular expressions. Most of the times you'll be able to reach your request through the above mentioned keyword search, in any-case, for advanced use cases we make regular expressions available as wel.

tip

You can active the regular expression filter and type .* to get a list of all the captured requests.

Smart filters​

You can use some labelled expression to target particular requests in the page. Below the smart filters supported:

  1. status: - use to filter by a particular HTTP response status, e.g. status:200 shows all the requests in the page with status 200.
  2. method: - use to filter by a particular HTTP method, e.g. method:POST shows all the requests in the page that have method POST (method value is case insensitive)
  3. rp:(my search query) - use to filter requests with a particular request payload (request body), e.g. rp:(getUsers) will show only requests that have the keyword "getUsers" in the request body. For example a graphql query often includes such keywords under the operationName property, you could use this smart filter to easily lookup the request with body "operationName": "getUsers" and have it immediately imported into a tweak rule.
tip

You can combine multiple smart filters, e.g. status:404 method:get api/v1 filters for all GET requests with status 404, where the URL contains "api/v1".

Note about data deletion​

After deleting all the requests from the extension , remember to retrigger all the requests from the browser tab, otherwise the search results will be empty (just like the devtools is emptied once you refresh the page).


Was this page helpful?