[
https://issues.apache.org/jira/browse/TS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-160:
-----------------------------
Attachment: TS-160.diff
This fixes the references I could find to "Traffic Edge", and cleans up a few
other things that doesn't make sense (but, this is in no way a complete cleanup
of the old domain examples etc.).
> Fix some "Traffic Edge" strings
> -------------------------------
>
> Key: TS-160
> URL: https://issues.apache.org/jira/browse/TS-160
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Priority: Trivial
> Fix For: 2.0.0a
>
> Attachments: TS-160.diff
>
>
> We should cleanup some of the old "Traffic Edge" strings, e.g.
> /export/apache/trafficserver.git/proxy/mgmt2/RecordsConfig.cc: {CONFIG,
> "proxy.config.product_name", "", INK_STRING, "Traffic Edge", RU_NULL,
> RR_NULL, RC_NULL, NULL, RA_NULL}
> /export/apache/trafficserver.git/proxy/mgmt2/web2/WebHttpRender.cc: // bug
> 52754: For Tsunami only, need to hack in Traffic Edge
> /export/apache/trafficserver.git/proxy/InkAPITest.cc: char
> *CONFIG_PARAM_STRING_VALUE = "Traffic Edge";
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
