[
https://issues.apache.org/jira/browse/TS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829723#action_12829723
]
Jason Giedymin commented on TS-140:
-----------------------------------
I think it's a really great feature to sense whether or not the user has
specified a path.
However I think having this is another added user config error/headache vector.
By making it only Fully Qualified, there is zero doubt by just reading the
config file what the situation is.
People (users, admins, etc) may have completely different prefixes which they
would like to install which is fine.
I'm in the belief that by only reading the config one should not have any
doubts about paths. It should be well defined outright at the beginning.
> path handling should be relative when there is no leading '/' in the config.
> ----------------------------------------------------------------------------
>
> Key: TS-140
> URL: https://issues.apache.org/jira/browse/TS-140
> Project: Traffic Server
> Issue Type: Bug
> Components: Config
> Affects Versions: 2.0.0
> Environment: All
> Reporter: George Paul
> Priority: Minor
> Fix For: 2.1.0
>
>
> All handling of paths should be relative when there is no leading '/'
> specified in the config.
> For example in the case of a relative path set to 'etc/trafficserver', this
> will get prepended with ${prefix} (e.g. /usr/local/, with the final path
> being /usr/local/etc/trafficserver), while a full '/etc/trafficserver' will
> not (i.e. the path stays /etc/trafficserver).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
