So, post the result of my research at the moment
TFPHTTPClientHTTP - worked
HTTPS - worked
HTTP with proxy - worked (
only trunk FPC)
HTTPS with proxy -
not workedSynapse HTTPClient THTTPSend classHTTP - worked
HTTPS - worked
HTTP with proxy - worked
HTTPS with proxy - worked (Windows)
HTTPS with proxy -
not worked (Linux: Debian x86_84) or
works with the hack (see post below)
Indy 10 HTTPClient TIdHTTPHTTP - worked
HTTPS - worked
HTTP with proxy - worked
HTTPS with proxy - worked
FurtherI wrote a basic client class emulating properties and functions (so far the ones I need) and separated the HTTP client from implementation. Accordingly, it will be possible to connect the required HTTP client by registering its implementation class. If anyone is interested - an example
herewhere
basehttpclient.pas - base
abstract http client class
fphttpclientbroker.pas -native TFPHTTPClient implementation
synapsehttpclientbroker.pas - Synapse THTTPSend implementation
indyhttpclientbroker.pas - Indy TIdHTTP implementation