@JonB said in How can I wait all request complate?: main() is no good for a Qt program I gave main() as an example. To show that there is a continuous data flow to the doSth function. @JonB said in How can I wait all request complate?: But if you really want to write your code to "block" and "wait" for a response, use a local QEventLoop instance and call exec(). This is at least an "efficient" way to do it. A couple of examples on stackoverflow illustrating just this for your QNetworkReply::finished case: https://stackoverflow.com/questions/29449561/qeventloop-proper-usage https://stackoverflow.com/questions/54694312/qeventloop-wait-for-only-local-events-not-main-loop-events Thank you I will look them

Hello, I also miss FTP since I switched to Qt 6. I don't like the idea of using libcurl because the more dependencies is added to an application, the more potential problems + the harder is the maintenance. I really hope that Qt will but back FTP support.

Need more information, such as Qt version, any messages you may see in the browser console.

Forgive me for bumping an old thread, but I too am interested in an answer to this question. As things stand I'm going to commit to using out-of-date APIs in order to accomplish this. But it'd be nice if there were an officially supported and modern way to make socket connections and HTTP / HTTPS requests using a specific network interface.

Not in the past few days, IIRC, OpenSSL 1.1 support started with 5.10 and the ore-built package switched to it during the 5.12 release cycle.

Hi, Usually you don't store the reply but rather connect its signals to lambdas, do the processing there and then call deleteLater on it once you are done.

Ahh sorry I thought an strace would help. It might take me a bit to get an actual stack trace as I'd have to set up my build environment with debugging symbols. The reason I was recreating QNetworkAccessManager is because I was under the impression that I needed to do so when I lost network access (m_mgr->networkAccessible() != QNetworkAccessManager::Accessible). That's what a user said on this stack overflow post. Is that incorrect? If I could just used something like setNetworkAccessible() that would avoid this whole mess. I've tested out removing the QNAM deletion and the exception does not occur. I guess I am sort of confused in general about what QNetworkAccessManager::NetworkAccessibility even represents? It's not going to alter the actual network state, NetworkManager handles that

Tested on another server, everything works fine

Another thing I notice is that QNetworkAccessManager manager is created just before the post request. This indicates to me that you are not handling any signal like finished(..). So how to you know that response has come back ?

@Lodhi-bhkr Sorry, but this is not a question. What did you try? What problems do you have? Please ask more specific questions. Looks like you asked here already: https://forum.qt.io/topic/120439/qt-code-to-send-data-on-postman-http-post-request

@raven-worx Yes, this is the code. I also did separate new code QNAM()->PUT(request,QFile*) & QNAM()->POST(request,QFile*) on my QT 5.4.1 setup. Everytime after executing the request application memory goes on increasing till it is equivalent to given file size(here I used 1GB file & memory increased by 1GB).

I had the same issue. The QIODevice::readAll() (which is called from QNetworkReply) function states this issue: This function has no way of reporting errors; returning an empty QByteArray can mean either that no data was currently available for reading, or that an error occurred. This function also has no way of indicating that more data may have been available and couldn't be read. The resolution is to connect QIODevice::readyRead to as per the documentation: connect(reply, &QIODevice::readyRead, this, [=]() { QByteArray response = reply->readAll(); qDebug() << response; });

@d1.psy so you want the cookies from the requests you already made with QtWebEngine? If so take a look at QWebEngineCookieStore (see it's signals) and "sync" the cookies into your QNAM.

resolved !! i've chenged m_pNetworkAccessManager->get(request); by request.setRawHeader("Content-Type", "application/x-www-form-urlencoded"); QByteArray par=""; m_pNetworkAccessManager->post(request,par);

sure i will reply with the project code

QNetworkRequest req(url); reply=qnam.get(req); QObject::connect(reply,SIGNAL(finished()),this,SLOT(slotFinished()));

@ksranjith786 said: Could you please provide guidelines or code snippet to use QNetworkAccessManager using multi threaded env. No, I can't, sorry. Not that I don't want to, but I don't know of any way you can control the number of threads QNetworkAccessManager uses internally (I think it's hardcoded). If I were to do multithreading with NAM I'd do it like you - thread the reply's processing. Unfortunately this bears no weight on the HTTP response time. On a related note, I would always prefer to use TCP/IP directly, as it provides much more fine-grained control of what's happening (including threading). The downside of that approach however, is that it'd require implementing the HTTP protocol by hand. Perhaps, as @p3c0 suggested, you could try to ask the question on the mailing list were you might get responses from the actual developers of the module. Kind regards.

@djee In My Way connectToHost To Http Server Not Working, So I Call QSslConfiguration::defaultConfiguration(); Instead.