1.2.216 - improvements in SE::Google::Modern and JS parsers, and many others

Discussion in 'News' started by Support Денис, Jun 11, 2018.

Tags:
  1. Support Денис

    Support Денис A-Parser Enterprise License
    A-Parser Enterprise

    Joined:
    Jun 12, 2017
    Messages:
    586
    Likes Received:
    185
    [​IMG]
    Improvements
    • A dependent task in the tasks chain now starts only when the results file is not empty
    • Retry added without changing proxy when failed sending ReCaptcha in SE::Google::Modern SE::Google::Modern
    • Added a ban proxy on receiving 403 response code in SE::Google::Modern SE::Google::Modern
    • The percentage of failed requests is now displayed relative to the number of completed requests
    • Added the ability to call the URL after the task is completed
    • Improved directory overview when selecting query files
    • Reduced Wait between get status and improved logging in Util::ReCaptcha2 Util::ReCaptcha2
    • Improved redirect processing
    • Added protection against infinite execution in JavaScript parsers
    • The function check_content in JS parsers are significantly increased
    • In the response of the info method API, the parameters workingTasks, activeThreads, activeProxyCheckerThreads are added
    Corrections due to changes in the issuance
    Corrections
    • Fixed logging after several pauses of the task
    • Fixed a bug due to which the query was considered failed when the serp was empty in SE::Google::Modern SE::Google::Modern
    • Fixed work with url containing a fragment # in Net::HTTP Net::HTTP
    • Fixed link parsing in HTML::LinkExtractor HTML::LinkExtractor
    • Fixed the work of the Pages count option in SE::Yandex SE::Yandex
    • Fixed selection of query files in Windows 10
    • Fixed a bug due to which sometimes it was impossible to delete the file with queries
    • Fixed displaying proxy checker in the config presets
    • Fixed encoding of some results in SE::Google::Suggest SE::Google::Suggest
    • Fixed a situation where settings from config.txt were not read
     

Share This Page