[
https://issues.apache.org/jira/browse/TS-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314892#comment-15314892
]
ASF subversion and git services commented on TS-4408:
-----------------------------------------------------
Commit 788f67e469097ebbba67b20e73a6a590cc31404e in trafficserver's branch
refs/heads/master from [~calavera]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=788f67e ]
TS-4408: Remove volume.config ordering constraints.
Make ConfigVolumes::BuildListFromString handle unordered options
when parsing volume.config. Remove ordering constraints in the
management API VolumeObj constructor.
This closed #618.
Signed-off-by: David Calavera <[email protected]>
> 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)
