squid-cache/squid

Squid Web Proxy Cache - Source Code

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 22nd, 2026
Created on September 27th, 2014
Open Issues & Pull Requests: 216 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 662
Total Stargazers: 3,106 (+0)
Total Subscribers: 72 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Squid is a web proxy cache that forwards HTTP, HTTPS, FTP, and other protocol requests while caching responses to reduce bandwidth consumption and improve response times for repeated requests.

Squid addresses the problem of redundant network traffic and slow content delivery by intercepting client requests, checking its cache for matching responses, and serving cached content when available. For requests not in cache, it forwards the request to the origin server, stores the response, and returns it to the client. The tool supports advanced features including ICAP protocol integration for content adaptation and eCAP for extensibility, allowing operators to customize request and response handling.

Organizations running internal networks, ISPs managing client traffic, or anyone operating a forward proxy infrastructure should consider Squid. It suits deployments where reducing upstream bandwidth and improving user-perceived latency matter, particularly in environments with repetitive access patterns. The tool is suitable for both small office networks and large-scale carrier deployments. Squid is a mature, established solution in the proxy cache category with a long operational history.

The project maintains active communication channels including dedicated mailing lists for users, developers, and security reports, with a public bug tracking system. Development discussions occur on a dedicated mailing list separate from user support.