You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2014/05/19 17:57:38 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 ]
Bryan Call updated TS-1992:
---------------------------
Fix Version/s: (was: 5.0.0)
5.1.0
> 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ć
> Fix For: 5.1.0
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)