Design and Implementation of a Cloud‑Based Shared Proxy Tool for Team Collaboration

The article introduces a cloud proxy built to overcome limitations of traditional packet‑capture tools such as Fiddler and Charles, which hinder rapid sharing of environment configurations and mock data among multiple developers and testers.

Two implementation paths are described: Solution 1 leverages the open‑source AnyProxy framework, extending its requestHandler and recordHandler modules to support multi‑user IP‑based isolation, real‑time request filtering, and QR‑code based configuration sharing; Solution 2 adopts Mitmproxy for the proxy layer and a separate web service for UI, using IP or user‑account identifiers to separate mock/host settings.

Configuration isolation is achieved by binding each request to a unique user identifier, allowing per‑user Mock and Host rules to be applied before forwarding. A sharing mechanism provides a page to query any user’s configuration and generate a QR code for quick import by others.

Data persistence stores all captured HTTP/HTTPS traffic in an embedded NeDB database, retaining full request logs for replay and analysis, while filtered valuable data are archived nightly for long‑term reporting.

Analytics modules generate reports such as version‑wise API coverage and abnormal response statistics, and a lightweight monitoring setup records process health and auto‑restarts the proxy when needed.

Benefits include reduced onboarding cost, efficient multi‑environment testing, richer data for debugging and documentation, and seamless integration with downstream platforms.

The article concludes that both solutions effectively transform a local proxy into a collaborative cloud service, and readers can combine the strengths of each approach to suit their own scenarios.