[
https://issues.apache.org/jira/browse/TS-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829417#action_12829417
]
Leif Hedstrom commented on TS-118:
----------------------------------
I think this looks good, I'm assuming you have tested all the cases? So, r=leif.
One comment though (feel free to file a separate bug on this if you prefer to
close this one):
To me, it's very confusing that setting a "path" config to say
/etc/trafficserver is still relative to ${prefix) (i.e. it becomes
/usr/local/etc/trafficserver). In any normal universe, an absolute path like
that would be used as such. So, my proposal is that we redo all handling of
such paths, so that
etc/trafficserver
gets prepended with ${prefix} (e.g. /usr/local/, with the final path being
/usr/local/etc/trafficserver), while
/etc/trafficserver
is not (i.e. the path stays /etc/trafficserver).
> SSL Cert location in trunk slightly misleading or confusing
> -----------------------------------------------------------
>
> Key: TS-118
> URL: https://issues.apache.org/jira/browse/TS-118
> Project: Traffic Server
> Issue Type: Bug
> Components: Config
> Environment: Ubuntu 9.10
> Reporter: Jason Giedymin
> Assignee: George Paul
> Priority: Minor
> Fix For: 2.0.0a
>
> Attachments: TS-118.patch, TS118_patch2.diff
>
>
> In Trunk, [records.config] reads:
> CONFIG proxy.config.ssl.server.cert.path STRING @prefix@/etc/@PACKAGE@
> However, @prefix is implied.
> Recommend:
> CONFIG proxy.config.ssl.server.cert.path STRING /etc/@PACKAGE@
> Patch provided with additional config comments provided.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
