[jira] [Updated] (TS-2244) Remove legacy proxy.config.log.search_log_enabled feature
[
https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Call updated TS-2244:
---
Summary: Remove legacy proxy.config.log.search_log_enabled feature (was:
remove legacy proxy.config.log.search_log_enabled feature)
> Remove legacy proxy.config.log.search_log_enabled feature
> -
>
> Key: TS-2244
> URL: https://issues.apache.org/jira/browse/TS-2244
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Logging
>Reporter: James Peach
>Assignee: Leif Hedstrom
> Labels: compatibility
> Fix For: 6.0.0
>
>
> While analyzing logging code, I came across the
> {{proxy.config.log.search_log_enabled}} setting. This enabled a hard-coded
> XML custom log format that may have been used to drive an Inktomi appliance
> feature.
> This has never been documented and is not generally useful to modern Traffic
> Server deployments. We should remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2244) remove legacy proxy.config.log.search_log_enabled feature
[
https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2244:
--
Fix Version/s: 4.1.0
> remove legacy proxy.config.log.search_log_enabled feature
> -
>
> Key: TS-2244
> URL: https://issues.apache.org/jira/browse/TS-2244
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Logging
>Reporter: James Peach
> Fix For: 4.1.0
>
>
> While analyzing logging code, I came across the
> {{proxy.config.log.search_log_enabled}} setting. This enabled a hard-coded
> XML custom log format that may have been used to drive an Inktomi appliance
> feature.
> This has never been documented and is not generally useful to modern Traffic
> Server deployments. We should remove it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-2244) remove legacy proxy.config.log.search_log_enabled feature
[
https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2244:
--
Fix Version/s: (was: 5.0.0)
6.0.0
I'm moving this out for 6.0.0, but definitely move it back to v5.0.0 if this
will get modified / removed for this release.
> remove legacy proxy.config.log.search_log_enabled feature
> -
>
> Key: TS-2244
> URL: https://issues.apache.org/jira/browse/TS-2244
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Logging
>Reporter: James Peach
> Fix For: 6.0.0
>
>
> While analyzing logging code, I came across the
> {{proxy.config.log.search_log_enabled}} setting. This enabled a hard-coded
> XML custom log format that may have been used to drive an Inktomi appliance
> feature.
> This has never been documented and is not generally useful to modern Traffic
> Server deployments. We should remove it.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (TS-2244) remove legacy proxy.config.log.search_log_enabled feature
[
https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-2244:
---
Fix Version/s: (was: sometime)
6.0.0
> remove legacy proxy.config.log.search_log_enabled feature
> -
>
> Key: TS-2244
> URL: https://issues.apache.org/jira/browse/TS-2244
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Logging
>Reporter: James Peach
> Fix For: 6.0.0
>
>
> While analyzing logging code, I came across the
> {{proxy.config.log.search_log_enabled}} setting. This enabled a hard-coded
> XML custom log format that may have been used to drive an Inktomi appliance
> feature.
> This has never been documented and is not generally useful to modern Traffic
> Server deployments. We should remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2244) remove legacy proxy.config.log.search_log_enabled feature
[
https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-2244:
---
Assignee: James Peach
> remove legacy proxy.config.log.search_log_enabled feature
> -
>
> Key: TS-2244
> URL: https://issues.apache.org/jira/browse/TS-2244
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Logging
>Reporter: James Peach
>Assignee: James Peach
> Fix For: 6.0.0
>
>
> While analyzing logging code, I came across the
> {{proxy.config.log.search_log_enabled}} setting. This enabled a hard-coded
> XML custom log format that may have been used to drive an Inktomi appliance
> feature.
> This has never been documented and is not generally useful to modern Traffic
> Server deployments. We should remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-2244) remove legacy proxy.config.log.search_log_enabled feature
[
https://issues.apache.org/jira/browse/TS-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2244:
--
Labels: compatibility (was: )
> remove legacy proxy.config.log.search_log_enabled feature
> -
>
> Key: TS-2244
> URL: https://issues.apache.org/jira/browse/TS-2244
> Project: Traffic Server
> Issue Type: Bug
> Components: Cleanup, Logging
>Reporter: James Peach
>Assignee: James Peach
> Labels: compatibility
> Fix For: 6.0.0
>
>
> While analyzing logging code, I came across the
> {{proxy.config.log.search_log_enabled}} setting. This enabled a hard-coded
> XML custom log format that may have been used to drive an Inktomi appliance
> feature.
> This has never been documented and is not generally useful to modern Traffic
> Server deployments. We should remove it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
