I've submitted a Qt bug report for this:

https://bugreports.qt.io/browse/QTBUG-119614
"SSL initialization is around 10 to 100 times slower in Qt 6"

Well WebAssembly is pretty strict, if you want to make https requests you need to use a proxy/bridge program that translates from websockets to http, it's installed on a PC on the same LAN as the WebAssembly PC (or on the same PC). For example you could use this one: https://github.com/novnc/websockify

https://stackoverflow.com/questions/58875159/how-to-ignore-ssl-certificate-errors-with-qwebengineview link helped me to resolve the issue. Now HTTPS page load after ignoring ssl warning is fine. Thanks for ideas :)

@Rizwan94 said in Interceptor in QT?:

I got to know that in java spring framework etc. We have interceptors which help process the request & response.

In QT, do we have anything similar that can be used.

Qt uses signals and slots: https://doc.qt.io/qt-5/signalsandslots.html

Currently for making REST api calls in my application i am making use of QNAM.

When you call get() or post(), QNAM returns a QNetworkReply object. Connect the QNetworkReply::finished() signal to a slot to process the reply. Remember to delete the QNetworkReply when you have finished processing.

@Pablo-J-Rogina thanks. Just looked into it. As the docs for QNetworkConfiguration state:

QNetworkConfiguration encapsulates a single access point or service network. In most cases a single access point configuration can be mapped to one network interface.

I deduce from that, that any call to QMediaPlayer::setNetworkConfigurations(QList<QNetworkConfiguration>) will not fix my problem. In fact, I gather from the information, that QNetworkConfiguration deals more with hardware-side networking & routing configurations than it does with specifics for transmission protocols.

This notion is strengthened by the fact, that there is no accessible public members for QNetworkConfiguration and the only available constructors are copy and default. Therefore, the only way accessible way to provide valid values to setNetworkConfigurations is by filtering QNetworkConfigurationManager::allConfigurations()). Then again, this method produces a list dependent on the host system, which indicates hardware specific settings.

Still, I got curious while reading the desciption for QNetworkConfiguration::ServiceSpecificPurpose, which states:

The configuration can be used for operator specific services (e.g. receiving MMS messages or content **streaming**).

For experimental purposes I filtered all available configurations of that type, which again didn't change anything for me.

(Also, be sure to check out my latest edit up top, if you care for more info)

@SGaist said in HTTPS POST performance:

Hi and welcome to devnet,

@wrekler said in HTTPS POST performance:

How relevant is knowing the server?

It is relevant because:

It might be sleeping if for example it's an heroku free tier that hasn't been used for some times. Therefore the first query will have to wait for the server to awaken thus it will be longer. It might require authentication which takes some time on first query to setup and allow to process. It might need to query some slow to start resource to answer your question etc.

Oh, I see. Well it is not a my server, it is a thirdy party server, so I can't answer to all that question. All I know is:

It is hosted on akamai.com Acqtually it require some authentication data that I give with POST data

So I think I can't optimize requests server side, all can I do is caching DNS/TCP/SSL requests but I don't know if Qt 5.11.2 actually implements all that suggestions

I encountered the same problem, have you found the solution? if so, could you tell me the answer please? it has confused me for a few days.

@Dooms said:

sslConfiguration

You don't seem to have actually associated the sslConfiguration object with the QSslSocket object.

You can set the cert/key files directly on the QSslSocket if that helps simplify your code for testing...

Hi,

Since it's username/password your original clientGUI::provideAuthenication should have worked however I would not have read the content of the reply just called setUser and setPassword

Use setRawHeader from QNetworkRequest with Authorization as the name