Accessing Https, host requires authentication message
-
Hi Sgaist,
Sorry for answering so late but I was outside. The request more specifically is this:
_Url= "https://myweb.com/Ob/places?INFO1=ABCDEF&password=012345&username=Mario"; QNetworkRequest request(_Url); QNetworkReply *myReply = nam->get(request);
I don't do any other thing...
-
It's not how you should do the request, search for "basic http authentication" and QNetworkAccessManager::authenticationRequired
-
@SGaist oh sorry!! I think you mean this:
I tried with:Constructor:
nam = new QNetworkAccessManager(this); QObject::connect ( nam, SIGNAL(authenticationRequired(QNetworkReply*,QAuthenticator*)), this, SLOT(onAuthenticationRequestSlot(QNetworkReply*,QAuthenticator*)) );
And then this, but it never gets into here...
void WPConfigs12::onAuthenticationRequestSlot(QNetworkReply *aReply, QAuthenticator *aAuthenticator) { qDebug() << "INSIDE "; aAuthenticator->setUser("Mario"); aAuthenticator->setPassword("012345"); }
-
You really should get more details from your colleague on how what he uses to handle user authentication
-
@SGaist Is it normal that the "INSIDE" qDebug message is not pritned? I mean... its like the connect doesn't work and maybe its because i did it wrong... (last time this happened to me was because I was working with threads and I forgot to start it so the connect failed.)
-
Your connect statement looks fine. Do you have any error message on the console ?
-
@SGaist No, nothing...In the compile output there is nothing wrong. I just had
QLayout: Attempting to add QLayout "" to WizardPage2"WizardPage2", which already has a layout
in Applicatiion output but this does not affect the program... and the connect itsself has anything it need to work because I have others that run with no problem. (Have what it needs = Q_OBJECT declared in header and so on).
That's why I asked if maybe I needed to start anything as it was a thread (If you work with threads and don't start them, you have the same problem) -
Unless you put your QNAM in a thread, no theres nothing special you need to do.
As a last restort, you can set the Authorization header yourself on the query -
Use setRawHeader from QNetworkRequest with Authorization as the name