* Merge from Debian testing (LP: #1016560). Remaining changes: + debian/control: - Update maintainer. - Suggests apparmor (>= 2.3) - Depends on ssl-cert ((>= 1.0-11ubuntu1) - Add transitional dummy packages + debian/squid3.upstart - Move ulimit command to script section so that it applies to the started squid daemon. Thanks to Timur Irmatov (LP: 986159) - Work around squid not handling SIGHUP by adding respawn to upstart job. (LP: 978356) + debian/NEWS.Debian: Rename NEWS.debian, add note regarding squid3 transition in 12.04 (LP: 924739) + debian/rules - Re-enable all hardening options lost in the squid->squid3 transition (LP: 986314) + squid3.resolvconf, debian/squid3.postinst, debian/squid3.postrm, debian/squid3.preinst, debian/squid3.prerm: - Convert init script to upstart + debian/patches/99-ubuntu-ssl-cert-snakeoil: - Use snakeoil certificates. + debian/logrotate - Use sar-reports rather than sarg-maint. (LP: 26616) + debian/patches/90-cf.data.ubuntu.dpatch: - Add an example refresh pattern for debs. (foundations-lucid-local-report spec) + Add disabled by default AppArmor profile (LP: 497790) - debian/squid3.upstart: load profile in pre-start stanza - add debian/usr.sbin.squid3 profile - debian/rules: + install debian/usr.sbin.squid3, etc/apparmor.d/force-complain and etc/apparmor.d/disable into $(INSTALLDIR) + use dh_apparmor - debian/squid3.install: install etc/apparmor.d/disable, force-complain and usr.sbin.squid3 - debian/squid3.preinst: disable profile on clean install or upgrades from earlier than when we shipped the profile
<p><b>Unable to forward this request at this time.</b></p>
24
24
</blockquote>
25
25
26
<p>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.</p>
26
<p>This request could not be forwarded to the origin server or to any parent caches.</p>
27
28
<p>Some possible problems are:</p>
29
<ul>
30
<li id="network-down">An Internet connection needed to access this domains origin servers may be down.</li>
31
<li id="no-peer">All configured parent caches may be currently unreachable.</li>
32
<li id="permission-denied">The administrator may not allow this cache to make direct connections to origin servers.</li>
33
</ul>
27
34
28
35
<p>Your cache administrator is <a href="mailto:%w%W">%w</a>.</p>