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).
FileCatalyst Web Proxy is not a general-purpose web proxy; it is a specialized middleware tool designed to solve a specific, expensive problem: transferring large files over high-latency networks. By bridging standard HTTP/HTTPS web traffic with the high-speed FileCatalyst UDP protocol, it eliminates the bottlenecks of TCP.
To understand the value of this product, one must understand the problem it solves. Standard web file uploads (HTTP) rely on TCP, which ensures delivery but suffers from "windowing" issues. Over long distances (high latency), TCP spends most of its time waiting for confirmation of receipt rather than sending data. filecatalyst web proxy
In some browser-based deployments, a specific is used. This servlet allows FileCatalyst web applications to function even when local domain resolution (like localhost.filecatalyst.net ) is restricted by local machine policies, ensuring users can still access accelerated transfers via their browser. FileCatalyst Reverse Proxy Quickstart Guide
Unlike standard web proxies, the FileCatalyst version is designed to handle the high-throughput, UDP-based protocol that makes FileCatalyst fast. FileCatalyst Web Proxy sits between the user’s web
Here is a step-by-step overview of how FileCatalyst Web Proxy works:
In the FileCatalyst Server Admin, add the unlimited.fc.proxy.reverseProxyHost property with the proxy’s IP. By bridging standard HTTP/HTTPS web traffic with the
FileCatalyst is an enterprise solution with enterprise pricing. It is not a budget tool. Organizations moving small files or operating on a LAN (low latency) will not see enough performance gain to justify the licensing costs. This is strictly a solution for high-latency, high-bandwidth environments.
While "Proxy" sounds simple, this requires careful architectural planning. You need a FileCatalyst Server or Workflow instance at the receiving end. Setting up the proxy rules, firewall exceptions for UDP traffic, and authentication bridges requires IT competency. It is not a "plug-and-play" appliance for junior admins.