[
https://issues.apache.org/jira/browse/TS-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274194#comment-15274194
]
ASF GitHub Bot commented on TS-4408:
------------------------------------
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/618#issuecomment-217472293
I haven't had time to look at this properly, but ``volume.config`` is not
(only) parsed by the management routines, it is parsed by
``ConfigVolumes::BuildListFromString``. I am pretty sure that there are generic
parsing routines for the key=value line format. I like the used of ``ink_atoi``
that you did here ... that's more convenient for the size field.
> volume.config is ordering sensitive
> -----------------------------------
>
> Key: TS-4408
> URL: https://issues.apache.org/jira/browse/TS-4408
> Project: Traffic Server
> Issue Type: Bug
> Components: Configuration
> Reporter: James Peach
> Fix For: sometime
>
>
> {{volume.config}} is sensitive to the ordering of its fields. For example,
> this doesn't work:
> {code}
> volume=1 size=50% scheme=http
> {code}
> but this does:
> {code}
> volume=1 scheme=http size=50%
> {code}
> All the key=value configuration files are supposed to be ordering-insensitive.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
