Filecatalyst Web Proxy ~upd~ Now

FileCatalyst Web Proxy sits between the user’s web browser and the destination server. It accepts standard HTTP uploads, strips away the TCP overhead, and tunnels the payload via the proprietary FileCatalyst protocol (based on UDP).

The proxy can be configured to require SSL for all incoming client connections, ensuring data is encrypted as it traverses the public WAN. How the Proxy Architecture Works filecatalyst web proxy

External clients (such as HotFolder or TransferAgent) connect to the proxy's IP address as if it were the actual FileCatalyst Server. FileCatalyst Web Proxy sits between the user’s web

The proxy receives the client's TCP commands and UDP data packets and tunnels them through to the internal server via the established back channel. Configuration and Requirements strips away the TCP overhead