The URL that is used to fetch and parse a web page. The protocol must be
HTTP defines a set of request methods to indicate the desired action to be performed for a given resource. Although they can also be nouns, these request methods are sometimes referred as HTTP verbs.
The User-Agent request header contains a characteristic string that allows the network protocol peers to identify the application type, operating system, software vendor or software version of the requesting software user agent.
Request headers containing more information about the resource to be fetched or about the client itself.
no additional custom headers will be sent by default
Will add Cookies to your request
will send no Cookies by default
Sets the total request timeout duration. A timeout of zero (
Configures the connection to (not) follow server redirects.
Ignore the document's Content-Type when parsing the response. If set to false, an unrecognized content-type will cause an IOException to be thrown. (This is to prevent producing garbage by attempting to parse a JPEG binary image, for example.)
Configures the connection to not throw exceptions when a HTTP error occurs. (4xx - 5xx, e.g. 404 or 500). An IOException is thrown if an error is encountered. If set to
Disable/enable TLS certificates validation for HTTPS requests.
All connections over HTTPS perform normal validation of certificates, and will abort requests if the provided certificate does not validate.
Set the maximum bytes to read from the (uncompressed) connection into the body, before the connection is closed, and the input truncated.
no maximum body size
For server-side rendered Websites, XML-responses you should always use the default mode because it's more performant (good old HTTP request).
If you need to parse client side rendered Websites (e.g. build with React.js, Vue.js, Angular or jQuery) try the DOM mode.