- netfence firmware versions 4.2.0, 4.2.1, 4.2.2, 4.2.3, 4.2.4
The requested page does possible use HTTP/1.1 and not HTTP/1.0 . HTTP/1.1 is supported up to squid 2.9 and is also included in release 3.0. For more details take a look on the squid roadmap http://wiki.squid-cache.org/RoadMap/Squid2.
The problem has been fixed with netfence 4.2.5. The "proxyNG" and the "flashProxy" uses the squid engine 3.1, which supports HTTP/1.1 .
If you us a previous netfence version or the standard "HTTP Proxy" or the "Secure Web Proxy", then there are two possible solutions for this problem:
Enter the value "about:config" into the address bar and search for "http" in the filter bar. Doubleklick on the parameter "network.http.accept-encoding" and delete all string-values from this parameter.
header_access Accept-Encoding deny all
header_access via deny all
header_access X-Forwarded-For deny all
For Secure Web Proxy set this three options in "Secure-Web-Proxy Settings" > "Advanced" at the end of the configuration dialog:
header_access Accept-Encoding deny all
header_access via deny all
header_access X-Forwarded-For deny all
You must enable the "no_accept_encoding_header" option to disable the HTTP/1.1 for the Secure Web Proxy. Enter the command line of the box, were the Secure Web Proxy is running and use the one of the needed commands above.
to enable "no_accept_encoding_header":
/opt/microdasys/bin/oemtool accountconfig 1 no_accept_encoding_header yes
to disable "no_accept_encoding_header" (default value):
/opt/microdasys/bin/oemtool accountconfig 1 no_accept_encoding_header no
to check if "no_accept_encoding_header" is enabled or disabled:
/opt/microdasys/bin/oemtool get accountconfig 1 no_accept_encoding_header
Note:
This HTTP/1.1 disable option for the Secure Web Proxy is available in Release 4.2.4 and above.