Minor enhancement for RFC violating response headers from some web-servers.
Some web-servers like apple.com respond with a 301 redirect response headers.
These headers do not contain the entity as mandated by RFC 2616.
SafeSquid now enforces a proper conversion of these headers.
The Links to the Patch are-
1. SafeSquid 32- Bit Versions
2. SafeSquid 64- Bit Versions
Patch Can be applied using following steps-
Step 1# Do Save Setting from Safesquid Interface and Take Backup of config.xml
cp /opt/safesquid/safesquid/config.xml /config.xml-bakcup-$(date +%F)
Step 2# Extract Download file and cd into latest Safesquid
tar -xzvf safesquid_latest.tar.gz
Step 3# Actual Upgrade Steps
/etc/init.d/monit stop; /etc/init.d/safesquid stop; ./patch.sh ; /etc/init.d/safesquid start ; /etc/init.d/monit start;
Note: - if you are not using monit then just use below command
/etc/init.d/safesquid stop; ./patch.sh ; /etc/init.d/safesquid start
If you are using SafeSquid for the first time you can follow SafeSquid Installation Steps.