[BUG]: QtWebEngine ignores login/password for proxy

[Ac314]

Brief description of the issue

(Related to #2273) QtWebEngine ignores login/password for proxy when used for previewing the article. So it seems it does not retrieve the credentials from the feed properties.

Some (maybe important) addition: sometimes the app prompts for login/password for proxy, I do not know what exactly triggers it. After you manually enter login and password the article previewing starts working OK so QtWebEngine is definitely utilizing the credentials. But after the app restart it "forgets" it.

How to reproduce the bug?

1. Start the app
2. Click on the article in articles list
3. Proxy is used but without credentials

What was the expected result?

Using the credentials.

What actually happened?

Not uses the credentials.

Debug log

Probably no need for that.

Crash dump

No crashes.

Operating system and version

RSS Guard

Version: 5.2.2 (built on Windows/AMD64)
Revision: stable
Variant: web
OS: Windows 10 Version 22H2
Qt: 6.10.3 (compiled against 6.10.3)

[martinrotter]

Provide debug log file, also double check %data%/web/proxies.pac file if you see anything blatantly wrong and/or share the file here also.

I tested this:

1. Set app-wide proxy or just feed proxy and open new web tab and navigate to some website -> works and asks for user/pass.
2. Set feed-wide proxy and fetch its articles -> works and uses user/pass set in feed settings.
3. Set feed-wide proxy and preview some of its articles which contains images from the feed host -> images load through proxy fine and user/pass is used properly from the feed.

It could be that maybe you have some more complex feed structure or something? Step by step definite guide including URLS etc to reproduce the problem would be nice, I cannot really reproduce easily right now.

I am testing with "pproxy" python package: python -m pproxy -l "http+socks5://127.0.0.1:1080#testuser:testpass" -vvv. I observed that SOCKS5 proxies really sometimes behave strange - feed suddenly stops working etc. HTTP proxy seems to work better. I checked codebase and its not in my code. Probably Qt/proxy handling is not that great.

Also, I have found out via GPT that, citing: "Chromium does not support SOCKS5 username/password authentication" - so this could be the problem you have?

[martinrotter]

https://chromium.googlesource.com/chromium/src/%2B/HEAD/net/docs/proxy.md?utm_source=chatgpt.com