How to send json-file to the address?

jsulm

@Mikeeeeee said in How to send json-file to the address?:

Okay, can you please tell me how I can run it asynchronously?

You already do. You need to connect a slot to https://doc.qt.io/qt-5/qwebsocket.html#connected signal and in that slot call

qDebug()<<myWebSocket.isValid();

"Or maybe the program can wait until a socket connection appears?" - why don't you simply use signals/slots?!

Mikeeeeee

I took the example code, and it says so:

SslEchoClient::SslEchoClient(const QUrl &url, QObject *parent) :
    QObject(parent)
{
    connect(&m_webSocket, &QWebSocket::connected, this, &SslEchoClient::onConnected);
    connect(&m_webSocket, QOverload<const QList<QSslError>&>::of(&QWebSocket::sslErrors),
            this, &SslEchoClient::onSslErrors);
    m_webSocket.open(QUrl(url));
}

There are signals and slots, I create an object of this class, but it does not connect. Why?

jsulm

@Mikeeeeee said in How to send json-file to the address?:

but it does not connect. Why?

You know, there is https://doc.qt.io/qt-5/qwebsocket.html#error-1 signal.
Did you connect a slot to it to see whether you get an error?

Also see https://doc.qt.io/qt-5/qwebsocket.html#errorString

J.Hilk

@Mikeeeeee said in How to send json-file to the address?:

QWebSocket::sslErrors

why the overload ? as far as I can see sslErrors has no alternatives to QList<QSslErrors>

https://doc.qt.io/qt-5/qwebsocket-members.html

Mikeeeeee

Tried to start an example "SslEchoClient", but it irzhe does not connect and does not display error messages.
In my project I connected the status output to the button:

#include "mainwindow.h"
#include "ui_mainwindow.h"

MainWindow::MainWindow(QWidget *parent) :
    QMainWindow(parent),
    ui(new Ui::MainWindow)
{
    ui->setupUi(this);

    myUrl = "wss://ws.binaryws.com/websockets/v3?app_id=xlY2chJRk0XoSL5";
    myWebSocket.open(QUrl(myUrl));
    qDebug()<<myWebSocket.isValid()<<myWebSocket.state();

}

MainWindow::~MainWindow()
{
    delete ui;
}

void MainWindow::on_testButton_clicked()
{
    qDebug()<<myWebSocket.isValid()<<myWebSocket.state()<<myWebSocket.error();
}

Debug return:
false QAbstractSocket::UnconnectedState QAbstractSocket::UnknownSocketError
false QAbstractSocket::UnconnectedState QAbstractSocket::UnknownSocketError
false QAbstractSocket::UnconnectedState QAbstractSocket::UnknownSocketError
false QAbstractSocket::UnconnectedState QAbstractSocket::UnknownSocketError

Why can't I even use the example "SslEchoClient" to connect to the websocket?

jsulm

@Mikeeeeee DO YOU HAVE ANY ERRORS WHEN TRYING TO CONNECT? After calling myWebSocket.open(QUrl(myUrl).
Did you connect a slot to https://doc.qt.io/qt-5/qwebsocket.html#error-1 as I suggested?
Is your onSslErrors called?

Mikeeeeee

I did, but debag doesn't say it was a error:

    myUrl = "wss://ws.binaryws.com/websockets/v3?app_id=xlY2chJRk0XoSL5";
    myWebSocket.open(QUrl(myUrl));
    //myWebSocket
    qDebug()<<myWebSocket.isValid()<<myWebSocket.state();
    connect(&myWebSocket, QOverload<QAbstractSocket::SocketError>::of(&QWebSocket::error),
        [=](QAbstractSocket::SocketError error){ qDebug()<<"i have error";});

Example "SslEchoClient" also no message, means no error, but the websocket is not connected.

Mikeeeeee

Do you have an example of "SslEchoClient" connecting to a websocket?

Mikeeeeee

Found this code. It is similar to worker.
You do not know any besoket on which it is possible to check operability?

Mikeeeeee

If I use the program with GitHub, I get an error: "WebSocket::processHandshake: Unhandled http status code 301"
Please tell me why and how to fix it?

jsulm

@Mikeeeeee If you use Google to search for "http 301" you will find https://en.wikipedia.org/wiki/HTTP_301 which tells you that 301 status code means "Moved Permanently is used for permanent URL redirection". What URL are you using?

Mikeeeeee

Trying to connect to websocket "wss://ws.binaries.com/websockets/v3?app_id=1089".
Yesterday, he was connected here, and today is not connected.
Apparently he works on a certain time.

Mikeeeeee

It looks like the bug of websocket. I connect to other web sites.