[
https://issues.apache.org/jira/browse/TS-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314363#comment-15314363
]
ASF GitHub Bot commented on TS-4408:
------------------------------------
Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/618
I did an initial review and some light testing of this.
@calavera the API I was referring to is ``parseConfigLine`` from
``MatcherUtils.cc``. It is not quite a generic parser but it will do the job
here and tidy up a lot. I'm probably going to merge this as it, so we can make
another PR for ``parseConfigLine``.
> 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)
