You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating from version 1.0.0 to version 2.1.0, I noticed that the proxy settings no longer take effect. I checked the code and identified the cause in the modification of the send_request_to_server method (f643313) due to Issue 189.
At first glance, it appears that the proxy address requires a scheme. That works, but it’s only by coincidence. The call proxy_uri.get_auth(proxy_userinfo, proxy_host, proxy_port); provides the hostname (for proxy_host) inadvertently by specifying the scheme. However, if you look into the proxy_uri variable, you will see that the hostname is stored in the m_auth property and not under m_path, where I believe it belongs.
Regards
Giuseppe
Repro steps
I specify the proxy settings like in the code below.
auto appConfig = realm::App::configuration();
appConfig.app_id = "myAppId";
// other configuration steps here...
realm::proxy_config proxyConfig;
proxyConfig.address = address = "proxy.example.com";
proxyConfig.port = 8888;
appConfig.proxy_configuration = proxyConfig;
auto app = realm::App(appConfig);
auto user = app.login(apiKey).get(); // Login throws an app_error exception saying "Invalid argument"
Version
2.1.0
Installation method
Manual compile
What Atlas Services are you using?
Atlas Device Sync
Compiler
MSBuild
OS and version
Windows 11
Code snippets
No response
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
What happened?
Hello,
After updating from version
1.0.0
to version2.1.0
, I noticed that the proxy settings no longer take effect. I checked the code and identified the cause in the modification of thesend_request_to_server
method (f643313) due toIssue 189
.At first glance, it appears that the proxy address requires a scheme. That works, but it’s only by coincidence. The call
proxy_uri.get_auth(proxy_userinfo, proxy_host, proxy_port);
provides the hostname (forproxy_host
) inadvertently by specifying the scheme. However, if you look into theproxy_uri
variable, you will see that the hostname is stored in them_auth
property and not underm_path
, where I believe it belongs.Regards
Giuseppe
Repro steps
I specify the proxy settings like in the code below.
Version
2.1.0
Installation method
Manual compile
What Atlas Services are you using?
Atlas Device Sync
Compiler
MSBuild
OS and version
Windows 11
Code snippets
No response
Stacktrace of the exception/crash you're getting
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: