[Bug 924739] Re: after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated

Adam Gandelman 924739 at bugs.launchpad.net
Fri Feb 24 20:57:01 UTC 2012


The following is a list of configuration options from 2.7 that have not
been ported to squid3, as of 3.19:

http://squidcache.cybermirror.org/squid/squid-3.1.19-RELEASENOTES.html#ss6.1

There are many.  Currently, squid3 will fail to parse config + start if
any of these yet-to-be-ported options exists in config.  So, while we
can work around the default config file location in packaging, there is
still two issues:

1. squid3 cannot parse the default config that ships with squid(v2).
There is a config directive 'broken_vary_encoding' included there that
will cause squid3 bailout on startup.  If there config file has been
modified by user (most likely), any of the options described in the
document linked above will cause squid to fail.

2.  Even if we patch squid to only warn on these config issues and
continue startup, the user expectations will be unmet in terms of
functionality.  If a user has come to depend on any of the yet-to-be-
ported features, their proxy will be broken or, at the least, behave
differently post-transition.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/924739

Title:
  after upgrade from oneiric to precise, previous squid config unused,
  cannot be used when relocated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/924739/+subscriptions



More information about the Ubuntu-server-bugs mailing list