Please contact the cache administrator if you have difficulties authenticating yourself or, if you are the administrator, read Squid documentation on cache manager interface and check cache log for more detailed error messages.

ERROR

The requested URL could not be retrieved

This request could not be forwarded to the origin server or to any parent caches. The most likely cause for this error is that the cache administrator does not allow this cache to make direct connections to origin servers, and all configured parent caches are currently unreachable.

ERROR

The requested URL could not be retrieved

The following error was encountered while trying to retrieve the URL: %U

Nie można przekazać tego żądania w chwili obecnej.

This request could not be forwarded to the origin server or to any parent caches. The most likely cause for this error is that the cache administrator does not allow this cache to make direct connections to origin servers, and all configured parent caches are currently unreachable.

ERROR

The requested URL could not be retrieved

The following error was encountered while trying to retrieve the URL: %U

Nie można przekazać tego żądania w chwili obecnej.

This request could not be forwarded to the origin server or to any parent caches. The most likely cause for this error is that the cache administrator does not allow this cache to make direct connections to origin servers, and all configured parent caches are currently unreachable.

ERROR

The requested URL could not be retrieved

The following error was encountered while trying to retrieve the URL: %U

Failed to establish a secure connection to %I

System zwrócił wartość: %E

This proxy and the remote host failed to negotiate a mutually acceptable security settings for handling your request. It is possible that the remote host does not support secure connections, or the proxy is not satisfied with the host security credentials.

ERROR

The requested URL could not be retrieved

The following error was encountered while trying to retrieve the URL: %U

Nie można ustanowić bezpiecznego połączenia z %I

System zwrócił wartość: %E

This proxy and the remote host failed to negotiate a mutually acceptable security settings for handling your request. It is possible that the remote host does not support secure connections, or the proxy is not satisfied with the host security credentials.

ERROR

The requested URL could not be retrieved

The following error was encountered while trying to retrieve the URL: %U

建立到 %I 的安全连接失败

系统返回以下内容：%E

This proxy and the remote host failed to negotiate a mutually acceptable security settings for handling your request. It is possible that the remote host does not support secure connections, or the proxy is not satisfied with the host security credentials.

@@ -218,14 +220,10 @@
to the IPv4 or IPv6 network that address belongs to. They are not permitted over the
IPv4-IPv6 boundary. Some ACL voodoo can however be applied to explicitly route the
IPv6/IPv4 bound traffic (DIRECT access) out an appropriate interface.
-

WCCP is not available (neither version 1 or 2). It remains built into squid for use with IPv4 traffic but IPv6 cannot use it.

+

WCCP is not available (neither version 1 or 2).
+It remains built into squid for use with IPv4 traffic but IPv6 cannot use it.

Transparent Interception is done via NAT at the OS level and is not available in IPv6.
Squid will ensure that any port set with transparent, intercept, or tproxy options be an IPv4-only
@@ -406,6 +404,26 @@
should be large enough to not require an explicit configuration in most
environments yet may be small enough to limit side-effects of loops.

This protocol uses port 80 and violates RFC 2616 by using an HTTP/1.1 compliant request and non-HTTP reply
+to start the stream transaction. If the reply is handled according to HTTP/1.1 RFC-compliance requirements
+the audio stream becomes jerky and contains regular 'popping' sounds.

+
+

Squid now processes the ICY replies natively according to the ICY requirements, not HTTP/1.1 requirements.
+The streamed data is not cacheable. All processing and access controls may be applied the same as for HTTP.

+
+

squid.conf change

+
+

Squid-2 contained a hack using the update_http0.9 squid.conf option to work around the
+unusual replies. This option is now obsolete.

+
+

The proto ACL type matches ICY once the reply has been received, before that the processing
+is only aware on an HTTP request. So the ACL will match HTTP.

Build Squid without advanced compiler error checking.
+This only affects the building process, enabling it to complete despite some
+possibly serious issues.
+Please do not use lightly, and please report the build issues which make it needed
+to the squid developers before doing so.

+

--disable-translation

Prevent Squid generating localized error page templates and manuals.
Which is usually tried, but may not be needed.

@@ -1740,6 +1768,18 @@

If it produces ongoing serious problems the external helper may be needed
but please report the bugs anyway.

+

--with-libexpat / --without-libexpat

+

Require libexpat XML parser to be built into Squid for ESI parsing.
+Build will fail if this option is used and the library is not present.
+Default is to auto-detect it when using ESI and ignore if not present.
+Use --without-libexpat to prevent it being auto-detected.

+
+

--with-libxml2 / --without-libxml2

+

Require libxml2 XML parser to be built into Squid for ESI parsing.
+Build will fail if this option is used and the library is not present.
+Default is to auto-detect it when building with ESI.
+Use --without-libxml2 to prevent it being auto-detected.