Auto Update behind an http proxy with credentials / error 23

[lab34]

Hello,
Thank you for your job, I like this browser !

I'm behind a corporate proxy.
When I want to check for update on the menu, it gives me "error 23"

I've did a Wireshark capture, and I saw that the proxy was answering http 407 - authentication required

Could it be possible to ask the credentials ?
Or, as a fall back, store the proxy address and credentials in an ini file ? (in the model of the startup command line)
Or, to use the http_proxy environnement variable ?

best regards

[Admin]

Thanks for your feedback.
Can we force the browser to bypass proxy?
e.g. Always direct link to our update server.

[lab34]

Thanks for your feedback.
Can we force the browser to bypass proxy?
e.g. Always direct link to our update server.

Hello,
no, on our company (and I think it's the same in other big companies), all internet access are going through a proxy, where you are authenticated with a personnal account (because they keep logs, they have HIPS, firewall, antivir, VPN are denied..., if you do something wrong you are clearly indentified...)

[Admin]

Hello,
no, on our company (and I think it's the same in other big companies), all internet access are going through a proxy, where you are authenticated with a personnal account (because they keep logs, they have HIPS, firewall, antivir, VPN are denied..., if you do something wrong you are clearly indentified...)

Well, we will try to make the updater inherit authentication from the browser.
I think it is not friendly to ask for authentication of proxy while upgrading.

[lab34]

Nice, thank you.

[bolleseb]

Dear all,

Thanks for your great browser.
I am still facing the issue described there.
I did not check with Wireshark but the behaviour is the same (trying to auto-update with "Check updates" menu) as well as the context (using Cent Browser behind a corporate proxy).
Has any fix being introduced since first message on this thread?

Thanks in advance.

Best regards,

--Sébastien

[Admin]

Dear all,

Thanks for your great browser.
I am still facing the issue described there.
I did not check with Wireshark but the behaviour is the same (trying to auto-update with "Check updates" menu) as well as the context (using Cent Browser behind a corporate proxy).
Has any fix being introduced since first message on this thread?

Thanks in advance.

Best regards,

--Sébastien

Sorry for the inconvenience.
This issue may be not easy to solve, our updater uses totally different way to connect to internet.
But we will try to figure it out.