System.Net.HttpClientComponent.TNetHTTPClient.ProxySettings
Delphi
property ProxySettings: TProxySettings read GetProxySettings write SetProxySettings;
C++
__property System::Net::Urlclient::TProxySettings ProxySettings = {read=GetProxySettings, write=SetProxySettings};
Properties
Type | Visibility | Source | Unit | Parent |
---|---|---|---|---|
property | public | System.Net.HTTPClientComponent.pas System.Net.HTTPClientComponent.hpp |
System.Net.HttpClientComponent | TNetHTTPClient |
Description
Proxy settings that the client component uses.
Platform Behaviour
The following table explains how the HTTP Client handles the system proxy settings on different platforms:
Platform | Behaviour |
---|---|
Windows |
The HTTP Client uses the system proxy settings. You can bypass the system proxy settings and you can also provide alternative proxy settings for the HTTP Client. To bypass the system proxy settings, create proxy settings for the HTTP Client and specify |
MAC OS X |
The HTTP Client always uses the system proxy settings. Even if you provide alternative proxy settings for the HTTP Client, the HTTP Client uses the system proxy settings. |
iOS |
The HTTP Client always uses the system proxy settings. Even if you provide alternative proxy settings for the HTTP Client, the HTTP Client uses the system proxy settings. |
Android |
The HTTP Client uses the system proxy settings. You cannot bypass those settings, but you can provide alternative proxy settings for the HTTP Client. |
Linux |
The HTTP Client uses the system proxy settings. You cannot bypass those settings, but you can provide alternative proxy settings for the HTTP Client. |
- Note: If the system does not specify any proxy settings (the connection is direct), that is also considered a "setting". For example, on iOS or MAC OS X with no system proxy settings, you cannot provide proxy settings for the HTTP Client. The settings that you provide are ignored because the system settings (the "no proxy" setting) are used.