Bablosoft

FingerprintSwitcher service 0.7.0 has been released | Сервис FingerprintSwitcher версии 0.7.0

Bablosoft News

  • supportS

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

    Bablosoft News
    13 Votes
    129 Posts
    30802 Views
    R

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

    DNS запросы для STUN и TURN серверов теперь выполняются через 8.8.8.8

    У Гугла будет возможность смотреть туда, куда нельзя ему смотреть?

  • supportS

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

    Bablosoft News
    27 Votes
    107 Posts
    23350 Views
    FastSpaceF

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

    @Igor от куда информация?

    Код сбора поменялся, я периодически чекаю чтобы исправить его и затем перелить его на свой домен
    Добавились функции со шрифтами и всё + 2 функции с расширениями Ublock и Metamask. Что они делают хз

    Скорее всего будет движок и шрифты в обнове. Большой обновы там не видно, учитывая сколько всего утекает и палится.

  • supportS

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

    Bablosoft News
    10 Votes
    41 Posts
    10755 Views
    TeamcaptchaaiT

    great

  • supportS

    Выпущена 2.0.0 версия FingerprintManager

    Bablosoft News
    8 Votes
    63 Posts
    15277 Views
    FoxF

    @Moris said in Выпущена 2.0.0 версия FingerprintManager:

    @Fox said in Выпущена 2.0.0 версия FingerprintManager:

    ссылки на него находятся в вашем личном кабинете

    На кого на него? Там же ссылки на дистрибутивы, а меня информация по 3-ей версии интересует.

    Или я что-то не правильно понял?

    FM3 это тот же FM2, но работающий на 24 версии BAS. Функционал идентичен, кроме пожалуй использования расширений браузера, эта возможность появилась только в 24 версии BAS и следовательно появилась в FM3.

  • supportS

    BrowserAutomationStudio 22.3.0 has been released

    Bablosoft News
    0 Votes
    13 Posts
    3159 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.