On 02/21/2017 08:22 PM, 周书林 wrote:
> And one more question, is there any checking mechanism for validity of
> config value?
Sure, most parsers check the tokens/strings they parse. The checks are
specific to the directive type and are often not comprehensive (e.g.,
may miss garbage after a valid
Thank you very much.
And one more question, is there any checking mechanism for validity of
config value?
For example, if config option "maximum_object_size_in_memory" is set as
1, how to check if this value is valid?
2017-02-22 0:52 GMT+08:00 Alex Rousskov :
On 02/21/2017 01:15 AM, 周书林 wrote:
> I found the src/cf.data.pre file, and read the content. But I still want
> to know how squid use this file to build the connection between the
> config file and the source code.
As you already know, the parser is generated. The generated code either
places
I found the src/cf.data.pre file, and read the content. But I still want to
know how squid use this file to build the connection between the config
file and the source code.
For example, a user's config file has a config option
"maximum_object_size_in_memory", in "src/cf.data.pre", it indicate
On 2017-01-13, 周书林 wrote:
> Why some of the configuration directives in official website cannot find in
> the source code? Some could find a relevant program variable in Class
> SquidConfig, while majority of the configuration directives cannot be found
> in the source
Why some of the configuration directives in official website cannot find in
the source code? Some could find a relevant program variable in Class
SquidConfig, while majority of the configuration directives cannot be found
in the source code, for example , directive "announce_port".
So how does