Content-Encoding type not allowed

[BarryStiefel]

Content-Encoding type not allowed



If you see this message in the logs, it is likely because your web browser supports alternative encoding schemes like gzip, deflate, or compress encoding of documents and is talking to a website that can support these methods. The end result is the download is faster. However, the HTTP Security Server needs a little help in supporting this.

In FireWall-1 4.1 SP2, it is possible to enable support for this by adding the following to the :props( section of $FWDIR/conf/objects.C or $FWDIR/conf/objects_5_0.C in NG :http_disable_content_enc (true) :http_disable_content_type (true)If it exists, remove the line that says:

:http_use_cvp_reply_safe (true)For guidelines on editing objects.C, see EditingObjectsDotC



In FireWall-1 4.1, you will also need to make a change on the firewall module in how it tries to communicate with the CVP server. Edit $FWDIR/conf/fwopsec.conf. Change the line that says: server 127.0.0.1 18181 auth_opsecso it says

server 127.0.0.1 18181 opsecBounce the gateway (fwstop; fwstart) and reload the security policy.



-- PhoneBoy - 31 Dec 2003

FAQForm FAQs.Class: ContentSecurityFAQs, TroubleshootingFAQs OperatingSystem?: FAQs.Version: