Bablosoft

Выпущена 21.4.1 версия BrowserAutomationStudio

Bablosoft News

  • supportS

    Выпущена 30.5.0 версия BrowserAutomationStudio

    Bablosoft News
    8 Votes
    26 Posts
    2858 Views
    FastSpaceF

    @Михаил96 там этот гироскоп еще работает не в реал тайм. Это моя одна из проверок в моем антифроде, наравне с fps

  • supportS

    Выпущена 24.5.0 версия BrowserAutomationStudio

    Bablosoft News
    17 Votes
    79 Posts
    16652 Views
    ?

    @DrPrime said in Выпущена 24.5.0 версия BrowserAutomationStudio:

    это нормальное поведение

    Если честно, то это не совсем корректное поведение, если мне нужно удалить файл, из которого ресурс берет данные, то это можно сделать, получив расположение ресурса и указать в действии Удалить Файл/Папку.

  • supportS

    Выпущена 23.2.0 версия BrowserAutomationStudio

    Bablosoft News
    20 Votes
    93 Posts
    22432 Views
    Y

    @support , смотрю, пожирнел ба(р)сик. А что за папка custom с похожим набором файлов?

  • supportS

    BrowserAutomationStudio 22.3.0 has been released

    Bablosoft News
    0 Votes
    13 Posts
    3450 Views
    supportS

    @gudolik

    Ok, here we go again. Your server is sensitive to input information. That is not rule, but exception on the web. Because when I tested it without proxy and without required headers, it just holds session infinite. That is not how servers works. They usually closes session with some error code. There are several cases, like headers, but not only headers. I don't own a server source code, so I can't say for sure about all things.

    This thing is also important.

    browser makes connection, sends request to ****, then make a couple of more requests, maybe makes more parallel connections, and then persist them for a long time, then maybe close. Browser also saves cookies from a first request and then sends it to ****/uk/account/loginmobile. HTTP client does only one connection and closes it immediately.

    Your initial case was "No response for a certain amount of time from http client if you are working with proxy".

    It is resolved. Because I've send you a project which resolves issue and always works. I've even provided a proxy to test.

    I've tried to understand, at least what problem we are trying to solve, but there is no answser for a direct question. You told about a history what you have tried, and what results did you get. That is not the issue, it is your experience.

    If you have certain error, that might be because of proxy, because of BAS, because of curl, or because of anything else. Issue must contain a steps, how it can be repeated and strict description. I can't see this.

    The only issue that I saw in your last message is:

    said in BrowserAutomationStudio 22.3.0 has been released:

    But adding -k or --insecure its fixes and thats what im asking you to do to add these in http curl requests. to fix the issue.

    Which is obviously not correct, because:

    --insecure is included by default. https://github.com/bablosoft/BAS/search?q=CURLOPT_SSL_VERIFYPEER&unscoped_q=CURLOPT_SSL_VERIFYPEER If the issue is with --insecure, it can easily can be fixed by adding it to curl command line, but it not. See failure examples, that I've sent to you. Missing --insecure command line param would give another error, something like "SSL peer certificate or SSH remote key was not OK" Issue reproduces on http:// scheme, which is obviously not influenced with this param.

    If you want to report about issue, please use following guide.
    https://community.bablosoft.com/topic/2707/how-to-correctly-report-about-error
    Further messages about this case, which doesn't match following guide will be ignored.

  • supportS

    Выпущена 21.7.1 версия BrowserAutomationStudio

    Bablosoft News
    27 Votes
    36 Posts
    12875 Views
    FastSpaceF

    Так я в ступоре.
    Ситуация.

    Был скомпилированный скрипт на версии 2.6xxx. Успешно обновлял его до версии 2.7.2. Однако на 2.7.2 словил такой баг, что при регистрации 90% аккаунтов ловили бан. Танцевал с бубном весь день и понять не мог, уже думал сайт меня спалил. В общем удалил BAS с сервака, с ПК, с сервера скрипт. Все важные действия пересоздал (Профиль - прокси - отпечаток). Заново все скомпилировал на версии 2.7.2. Результат на лицо после регистрации банят только 30% аккаунтов, но всю равно это не комильфо. Откатился к версии пораньше. Опять все заново скомпилировал. Ничего не банит (???)

    В общем впервые столкнулся с проблемой новой версии. Что-то с отпечатком стало не то и теперь сайт банит часть отпечатков.