ChromeRuntime and Proxy

[dilfich]

Hi, it seems like a similar question was raised, but I didn't find something.
Namely, the problem with the proxy for which authorization is required, how to solve it?

[dilfich]

I tried to add a header, but even in normal mode it doesn't work for some reason. Error ERR_INVALID_ARGUMENT

Code: Select all

...BeforeResourceLoad
....
TempNewMap.Append('Proxy-Authorization', 'Basic ZnJlZXVzZXIxOmZyZWV1c2VyMQ==');
TempNewMap.Append('Proxy-Connection', 'keep-alive');

This is how the connection of one of the VPN extensions looks like

[salvadordf]

The Chrome runtime mode is experimental and some features don't work yet.

Try using command line switches like --proxy-server with this value http://<user>:<pass>@<host>:<port>/, for example :

Code: Select all

GlobalCEFApp.AddCustomCommandLine('--proxy-server', 'http://username:password@myproxy.com:80');

That code line needs to be added before the GlobalCEFApp.StartMainProcess call.

[dilfich]

This is certainly not a solution, but it doesn't work either.

ERR_NO_SUPPORTED_PROXIES

GlobalCEFApp.AddCustomCommandLine('--proxy-server', 'http://0401:oLEFKa@86.18.202.21:7952');

Is it possible to add headers via devtools? I tried, but I couldn't add them at all.

Code: Select all

tab.call_method("Network.setExtraHTTPHeaders", headers={"Authorization": "Basic " + context.base64_message})

Code: Select all

  TempList.SetString('{"Authorization": "Basic 12345"}');
  TempParams.SetValue('headers', TempList);
  Chrom.ExecuteDevToolsMethod(0, 'Network.setExtraHTTPHeaders', TempParams);

[dilfich]

It turned out to add headers, but it still doesn't work

Code: Select all

 Chrom.ExecuteDevToolsMethod(0, 'Network.enable', nil);

  TempHeaders := TCefDictionaryValueRef.New;
  TempHeaders.SetString('Proxy-Authorization', 'Basic ZX45645gUZLYTduM0g=');
  TempHeaders.SetString('Proxy-Connection', 'keep-alive');

  TempParams.SetDictionary('headers', TempHeaders);
  Chrom.ExecuteDevToolsMethod(0, 'Network.setExtraHTTPHeaders', TempParams);

The problem is not only with the "Chrome runtime" in normal mode does not work either
ERR_INVALID_ARGUMENT

[dilfich]

And how to load the extension in ChromeRuntime? It seemed to work before.

[salvadordf]

Try to use the command line switch with one of these Chromium builds :
https://chromium.woolyss.com/

If it works in Chromium, it should also work in CEF unless there's a new bug or a regression.

These kinds of problems happen with experimental code.

[dilfich]

It doesn't work, it's probably been like this for a long time.

Thorium_AVX2_111.0.5563.111
But authorization works if you save the login \ password in the extension. Proxy Auto Auth

How do I add an extension here in Chrome Runtime mode? Previously, it was possible.

And error ERR_INVALID_ARGUMENT due to a security breach of changing headers sort of.

[salvadordf]

It doesn't work, it's probably been like this for a long time.
Thorium_AVX2_111.0.5563.111
But authorization works if you save the login \ password in the extension. Proxy Auto Auth

If an official Chromium build can't use that proxy and you need to install an extension then all you can do is try to reverse-engineer that extension to try to replicate what it does.

How do I add an extension here in Chrome Runtime mode? Previously, it was possible.
And error ERR_INVALID_ARGUMENT due to a security breach of changing headers sort of.

I have a limited experience with the Chrome runtime mode and I only installed an extension from the chrome extension store a few months ago.

Please, remember that CEF4Delphi is only a CEF wrapper, which includes Chromium. Some features are beyond the scope of the CEF4Delphi project.

[dilfich]

If an official Chromium build can't use that proxy and you need to install an extension then all you can do is try to reverse-engineer that extension to try to replicate what it does.

The problem is not in using a proxy, but in authorizing it.

As soon as the Chrome Runtime mode appeared, it was possible to install the extension, how to do it now?
91 (Mini Browser - CEF4Delphi) version of chrome on the screenshot.



There is an extension in the archive, it is definitely working.