Database |> Language |> Keywords |> Assignable |>
PROXY
Contents
Note: This is a feature that’s only enabled for our enterprise customers. If this interests you, reach out to book a demo.
Definition
When you want to leverage proxies as part of dealing with antiscraping measures then you can indicate so explicitly in the code you’re interested in leveraging them with. This sets it so requests performed by a traverser are done through a proxy instead of where our infrastructure is hosted.
Usage
To use proxies, simply ASSIGN to the PROXY keyword.
PROXY <| your_preferred_proxy_setting |
Available proxy settings
We offer two settings for leveraging proxies: ON and FALLBACK.
ON
When you’d like to set that all requests should be done using a proxy from the get-go, then assign the value ON to PROXY.
PROXY <| ON |
FALLBACK
When you’d like to set that all requests should proceed like they’d normally would but, when data or content in a page accessibly indicates that a request was blocked by antiscraping measures, to then attempt again with a proxy, then assign the value FALLBACK to PROXY.
PROXY <| FALLBACK |
Example
Here’s an example query where we retrieve the tagline from the landing page for the Free Software Foundation with it set to fallback on using a proxy if or when antiscraping content is received on first try.
PROXY <| FALLBACK |
fsf <| https://www.gnu.org/home.en.html |
tagline <| h2.first |
FROM fsf
|> SELECT tagline
