ExeOutput 2019 and Proxy

Hi
I’m using leaflet.js in my app however in thecompany environment the images/maps is not downloaded.
How can I use the proxy from ExeOutput

  1. from Chromium (javascript)
  2. from Php scripts
    to achieve the external links?

Proxy can be configured by the following JS code:

exeoutput.RunHEScriptCode('begin SetUIProp("crm", "ProxyServer", "1.2.3.4"); SetUIProp("crm", "ProxyPort", "1234"); end;');

Other properties available are:
ProxyType (from 0 to 4):
CEF_PROXYTYPE_DIRECT = 0;
CEF_PROXYTYPE_AUTODETECT = 1;
CEF_PROXYTYPE_SYSTEM = 2;
CEF_PROXYTYPE_FIXED_SERVERS = 3;
CEF_PROXYTYPE_PAC_SCRIPT = 4;

ProxyScheme, ProxyUsername and ProxyPassword.

Hi
I’m trying 2 method to set ProxyType ro autodetect

Application Settings->Components->Rendering Engine
AdditionalChromiumArgs --proxy-auto-detect

  1. assign function to the menu

procedure getproxy;
begin
SetUIProp(“crm”, “ProxyType”, “1”);
MessageBox(ord(GetUIProp(“crm”, “ProxyType”)),“ProxyType”,MB_OK);
end;
–> returning 0

Both method make me no success in settings - even the answer copied to the debugger make no success.
What am I doing wrong?

Try StrToInt instead of Ord

Hi
Thanks for answer. However I’m opening the Development Tools–>Console then:

exeoutput.RunHEScriptCode(‘begin SetUIProp(“crm”, “ProxyType”, “2”); end;’);
exeoutput.RunHEScriptCode(‘begin MessageBox(IntToStr(GetUIProp(“crm”, “ProxyType”)),“ProxyType”,MB_OK); end;’);

And return is still 0 --> and system proxy is not used by Chromium.
I’ve double check - also for “1” Autodetect is not visible as change - nor the traffic is not forwarded to proxy.

Is possible to add to Chromium some of Chrome extension (i’m checking the Chrome with Proxy Switcher add-in and Chrome working correctly behind the proxy in my organization. ExeOutput has no out access even when I trying to change the ProxyType options as You answer…
Any other suggestion to go via proxy?

even putting --proxy-auto-detect in Application Settings–> Rendering Engine ->AdditionalChromiumArgs give NO success :frowning:

We’re checking the problem with the proxy configuration

I’ve tried to comple with v 2.2.1 and works perfectly thought the proxy without any additional configuration needed in exeoutput

Now proxy is working as expected in ExeOutput 2019.1.
A new topic was added to the doc:
https://www.exeoutput.com/help/proxy-settings