Frankly, I forgot about it.

Then it also depends also on what tools fits best your needs. There's no silver bullet that will cover everything you need.

Also limiting yourself to only one language is not a good idea in the long run. There are good and bad things in every language thus knowing more than one allows to have a better grasp at what can be done, how easy/hard the maintenance would be etc.

Hi and welcome to devnet,

That's a question you should bring to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

@gollum
IIRC the authenticationRequired signal will be emitted when the HTTP response contains a WWW-Authenticate header.
HTTP401 is just an error code that you are not allowed to view this resource. So the webserver/webapplication doesn't even ask you to authenticate.

@gollum
Sorry I still don't understand who's authenticating where and how is oauth2 involved in all this.

I could use cookies as well which might make things easier.

I would think you not only could, but rather need to use cookies. How else will you distinguish between clients connected to you PHP service?

Use setRawHeader from QNetworkRequest with Authorization as the name

I have. Usually all my projects get inspired by either the examples or some other project that someone has put on the web. Its just that sometimes I have trouble moving them to the next level, just like with this one.