EACDF: Edge Authentication based Content Distribution Framework

How does EACDF run?

This animation shows the main process the system does:

ClientEdge WorkerOrigin Server403① Requests only need Edge Framework.② Requests need contents from origin server.③ Requests cant be proccessed by Edge Framework

Beside that, this system can also function as a flexible API gateway. It unifies requests from different vendors — for example, converting an OpenAI‑format request to Anthropic’s Claude API or aggregating multiple map services into a single endpoint. The edge worker supports replaceable encryption (RC4, AES‑GCM, etc.), optional database integration for user management, and built‑in rate limiting (e.g., 100 requests per minute or limited token usage). Moreover, the framework includes a lightweight WebUI that allows administrators to check token status, generate new tokens, and even host small web applications. All these features are added without changing the core authentication logic, keeping the system both lightweight and highly extensible.