Advanced

Send request directly

In case you want to send a request directly without going through the scheduler in Crawler, try the code below. direct takes the same options as queue, please refer to options for detail. The difference is when calling direct, callback must be defined explicitly, with two arguments error and response, which are the same as that of callback of method queue.

Work with bottleneck

Control rate limit for with limiter. All tasks submit to a limiter will abide the rateLimit and maxConnections restrictions of the limiter. rateLimit is the minimum time gap between two tasks. maxConnections is the maximum number of tasks that can be running at the same time. Limiters are independent of each other. One common use case is setting different limiters for different proxies. One thing is worth noticing, when rateLimit is set to a non-zero value, maxConnections will be forced to 1.

Normally, all limiter instances in limiter cluster in crawler are instantiated with options specified in crawler constructor. You can change property of any limiter by calling the code below. Currently, we only support changing property 'rateLimit' of limiter. Note that the default limiter can be accessed by c.setLimiterProperty('default', 'rateLimit', 3000). We strongly recommend that you leave limiters unchanged after their instantiation unless you know clearly what you are doing.

options.priority: Number Priority of this request (Default 5). Low values have higher priority.

Retry options

options.retries: Number Number of retries if the request fails (Default 3),

options.retryTimeout: Number Number of milliseconds to wait before retrying (Default 10000),

Server-side DOM options

options.jQuery: Boolean|String|Object Use cheerio with default configurations to inject document if true or "cheerio". Or use customized cheerio if an object with Parser options. Disable injecting jQuery selector if false. If you have memory leak issue in your project, use "whacko", an alternative parser,to avoid that. (Default true)

Charset encoding

options.forceUTF8: Boolean If true crawler will get charset from HTTP headers or meta tag in html and convert it to UTF8 if necessary. Never worry about encoding anymore! (Default true),

options.incomingEncoding: String With forceUTF8: true to set encoding manually (Default null) so that crawler will not have to detect charset by itself. For example, incomingEncoding : 'windows-1255'. See all supported encodings

Cache

options.skipDuplicates: Boolean If true skips URIs that were already crawled, without even calling callback() (Default false). This is not recommended, it's better to handle outside Crawler use seenreq

Http headers

options.rotateUA: Boolean If true, userAgent should be an array and rotate it (Default false)

options.userAgent: String|Array, If rotateUA is false, but userAgent is an array, crawler will use the first one.