You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Igor Galić (JIRA)" <ji...@apache.org> on 2013/07/02 16:42:20 UTC
[jira] [Updated] (TS-1992) examine mgmt/RecordsConfig.cc, add
validation where it makes sense
[ https://issues.apache.org/jira/browse/TS-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Galić updated TS-1992:
---------------------------
Summary: examine mgmt/RecordsConfig.cc, add validation where it makes sense (was: examine ./mgmt/RecordsConfig.cc and validation where it makes sense)
> examine mgmt/RecordsConfig.cc, add validation where it makes sense
> ------------------------------------------------------------------
>
> Key: TS-1992
> URL: https://issues.apache.org/jira/browse/TS-1992
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Reporter: Igor Galić
>
> example:
> {code}
> {RECT_CONFIG, "proxy.config.http.cache.required_headers", RECD_INT, "2", RECU_DYNAMIC, RR_NULL, RECC_NULL, NULL, RECA_NULL}
> {code}
> We should change this to
> {code}
> {RECT_CONFIG, "proxy.config.http.cache.required_headers", RECD_INT, "2", RECU_DYNAMIC, RR_NULL, RECC_NULL, "[0-2]", RECA_NULL}
> {code}
> which are the valid values for this config.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira