با سلام از کدام squid راضی هستید ...

[ccna]

با سلام از کدام squid راضی هستید ...

---

موضوعات مشابه:

• تفاوت روتر بورد ، نانو استیشن و پاور استیشن
• تفاوت پاور استیشن با نانواستیشن
• فرکانس نانو استیشن باید چند بزاری ؟
• نحوه انتقال کاربران squid به یک سایت خاص تعیین شده در squid server
• ساخت سرویس start squid برای squid compile شده

---

[neynef]

من از 2.5

[Alux]

ارزشیابی اینجوری شو ندیده بودم
مسلمه که ورژن 2.6 کارایی خیلی بهتری از 2.5 داره

اگه نداشت که اونهمه روش کار نمی کردند یه ورژن دیگه بدن بیرون

[darklove]

فرقی نداره

[kingmkh]

فرقی نداره

پس حتما 2.5 هم با 2.4و2.3و.... 2 فرقي نداره

اونا هم از رو بيكاري ريويژن ميدن بيرون

Key changes from squid 2.5

• Major improvements to the way that Squid handles web proxy, accelerated and transparent proxy requests to make it easier to configure transparent and acceleration functionality. The default behaviour is to function as a standard HTTP proxy on each port that Squid is configured to listen on, but in addition in this release the keywords "accel" and "transparent" can be specified after each port to indicate to Squid the functionality that is to be enabled on that port. This means that the old config directives relating to httpd_accel_* are now deprecated. See below for more details about these options.
• WCCPv2 support multiple cache engines registering with multiple WCCP routers and switches. WCCPv2 is preferred over WCCPv1 for performance and flexibility reasons if your router or switch is able to support it (all recent versions of IOS do so). Initially WCCPv2 under Linux is limited to registration with only one router due to kernel limitations in more recent versions, although this will be addressed in a future release of Squid.
• TPROXY totally transparent proxy support under Linux, which to allow Squid to appear totally invisible to both client and server systems when transparently caching requests. This works by spoofing the source and destination address to both the client and server.
• Support for Etag and Vary HTTP headers. This further moves Squid towards HTTP/1.1 compliance. The Vary header field is used for improved caching and delivery of customized content to end clients, and the Etag is used similar to an MD5 checksum between client and server to determine if a web page has changed since it was last retrieved.
• Collapsed forwarding, which gives Squid the ability to intelligently merge client requests for objects into one request to the server. Of particular benefit in accelerator setups but also provides some benefits to non accelerator setups.
• Support for epoll under Linux and kqueue under FreeBSD, which gives Squid the ability to handle many many more concurrent requests with lower CPU overhead. This feature is of particular benefit to very busy caches as the poll() and select() routines do not scale anywhere near as well as epoll and kqueue does under high loads.
• SSL assisted hardware encryption making use of OpenSSL functionality within Squid.
• Logging enhancements to allow even greater customization of the way Squid logs requests in the access-log or to syslog if required
• Authentication enhancements including Negotiate/Kerberos support, extra workarounds for NTLM clients and others using Microsoft Integrated Login.
• Additional external_acl parameters to support SSL and even more client side parameters.
• ACL changes in conjunction with SSL changes which have been merged, to allow matching based on SSL certificate parameters.
• Improvements to Cygwin support for users who wish to run Squid in a Microsoft Windows/Cygwin environment as a system service.
• New authentication helpers:
  • Digest LDAP helper
  • Native Windows basic, NTLM and negotiate helpers
  • External acl helpers for session monitoring and native Windows group membership check
• HTCP significantly cleaned up and added support for the CLR operation to purge contents from the cache
• Support for parsing X-Forwarded-For headers allowing access controls to be based on the real client IP even if behind secondary proxies
• Support for proxying of Microsoft Integrated Login (NTLM & Negotiate) connection oriented authentication schemes, enabling access to servers or proxies using such authentication methods.
• Support for the Linux TPROXY patch allowing Squid to masquerade using the clients original IP address
• urlgroups, tagging URLs for redirection and access controls, and divides the cache allowing different users to get different results for the same URL.
• Optional automatic monotoring of cache peers and configured origin servers
• SSL client support, allowing both http->https gatewaying and SSL encrypted peers (both origin servers and proxies).
• Full ETag/Vary based caching, allowing efficient caching of server driven content negotiation.
• Customizable access log format
• Selective access logging, and ability to log to more than access log possibly in different formats
• New more efficient helper protocol allowing for multiple concurrent lookups to the same helper
• Ability to rewrite Location headers (redirects sent by servers)

[lindows]

فرق squid stable2 با Devel 3 چیه؟