3. define a sane overall syntax, ignoring backwards compatibility, and
supply a translation tool which can be invoked as a filter
automatically if a legacy syntax is detected.
On Fri, Sep 14, 2012 at 1:22 AM, Marcus Kool
marcus.k...@urlfilterdb.com wrote:
On 09/13/2012 07:16 PM, Alex
On 14/09/2012 10:16 a.m., Alex Rousskov wrote:
Hello,
As you know, most old squid.conf options cannot handle spaces in
parameter values as they do not support quoted strings or other ways of
escaping the space separator. A few new options, support quoted strings,
but many old ones do not.
On 09/13/2012 05:22 PM, Marcus Kool wrote:
On 09/13/2012 07:16 PM, Alex Rousskov wrote:
2) Add squid.conf directives to turn the new parsing behavior on and off
for a section of the configuration file. This is also 100% backward
compatible but difficult to introduce gradually -- admins will
On 09/13/2012 09:19 PM, squ...@treenet.co.nz wrote:
I think your idea of file: schema to load files is hood. Or a -f flag
like the i flag.
The flag does not work for cases where two files are included:
acl foo bar file:/squid/condition1 file:/squid/condition2
I also think do that
On 09/14/2012 01:23 AM, Kinkie wrote:
3. define a sane overall syntax,
This may be a good time to do that indeed, so that we do not subject
admins to two or more syntax upgrades. I can sketch the rules based on
the ideas in the post that opened this thread.
ignoring backwards compatibility,
On 09/14/2012 05:41 AM, Amos Jeffries wrote:
On 14/09/2012 10:16 a.m., Alex Rousskov wrote:
Hello,
As you know, most old squid.conf options cannot handle spaces in
parameter values as they do not support quoted strings or other ways of
escaping the space separator. A few new options,
On 15/09/2012 2:23 a.m., Alex Rousskov wrote:
On 09/14/2012 05:41 AM, Amos Jeffries wrote:
On 14/09/2012 10:16 a.m., Alex Rousskov wrote:
Hello,
As you know, most old squid.conf options cannot handle spaces in
parameter values as they do not support quoted strings or other ways of
fre 2012-09-14 klockan 08:23 -0600 skrev Alex Rousskov:
Interesting. I did not expect much support for this, but two out of
three responses so far suggest this approach, essentially. When the dust
settles, perhaps we should post to squid-users as well to get more feedback?
clarity have higer
Hello,
As you know, most old squid.conf options cannot handle spaces in
parameter values as they do not support quoted strings or other ways of
escaping the space separator. A few new options, support quoted strings,
but many old ones do not. This is not going to be pretty because there
is no
FYI: There is a 2002 thread on squid-dev about the same problem. Not
sure whether any of the posted patches made it into Squid2, but the
discussion is worth reading anyway:
http://www.squid-cache.org/mail-archive/squid-dev/200211/0153.html
Alex.
On 09/13/2012 07:16 PM, Alex Rousskov wrote:
2) Add squid.conf directives to turn the new parsing behavior on and off
for a section of the configuration file. This is also 100% backward
compatible but difficult to introduce gradually -- admins will expect
everything inside a quoted strings
11 matches
Mail list logo
