Passive mode *Should not* need any firewall hole poking, at the Client
end.
That's the beauty of Passive mode! The client only ever makes outgoing
connections, it never has to receive an incoming one. Any half decent
firewall or NAT router, will handle all that transparently. It's worth
Any half decent firewall or NAT router, will handle all that
transparently.
That is correct for normal FTP, where the router can read the control
channel and check the internal IP address and translate it to an external
address, but not for SSL since the control connection is encrypted and
can
Hi,
Could someone please explain,
what this means?
Bomb('Add USE_SSL in the define section in project options');
This is in the Server demo project.
thanks in advance
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Could someone please explain,
what this means?
Bomb('Add USE_SSL in the define section in project options');
The code in the unit where such line is included is intended to be compiled
using the USE_SSL symbol defined at the project level. The line is there to
trigger a compilation error