How to retry requests that were blocked

v3.0

URL Requests that were blocked by HUMAN don’t reach your server. Therefore, after the user solves the challenge you may want to retry those requests. You can configure the behavior of the SDK when requests are blocked:

1. Delay response until challenge is solved or cancelled - setting this in the policy will delay the error response to your request’s handler until the user solves or cancels the challenge. Then, the error you will receive contains the information regarding the challenge result (solved or cancelled).

1
policy.urlRequestInterceptionType = .interceptWithDelayedResponse

2. Intercept and retry request - setting this in the policy will delay the error response to your request’s handler until the user solves or cancels the challenge. In addition, when the challenge is solved, the SDK will send the original request one more time. Your request’s handler should receive the response from your server without knowing that the request was blocked and sent again. You should note that when the challenge is cancelled or when the second request is also blocked, then the behavior will be the same as the “delay the response until the challenge is solved or cancelled” configuration.

1
policy.urlRequestInterceptionType = .interceptAndRetryRequest

How to disable the URL request’s timeout

URLSession:

1
var urlRequest = URLRequest()
2
urlRequest.timeoutInterval = 0

Alamofire:

1
AF.request("<url>", headers: HTTPHeaders(headers)) { $0.timeoutInterval = 0 }