[ 
https://issues.apache.org/jira/browse/TS-1882?focusedWorklogId=28535&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28535
 ]

ASF GitHub Bot logged work on TS-1882:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Sep/16 21:54
            Start Date: 08/Sep/16 21:54
    Worklog Time Spent: 10m 
      Work Description: Github user jpeach commented on a diff in the pull 
request:

    https://github.com/apache/trafficserver/pull/971#discussion_r78096463
  
    --- Diff: lib/records/I_RecCore.h ---
    @@ -168,11 +169,15 @@ int RecGetRecordBool(const char *name, RecBool 
*rec_byte, bool lock = true);
     //------------------------------------------------------------------------
     // Record Attributes Reading
     //------------------------------------------------------------------------
    +// Values with names that have this prefix are exempted from being 
considered "unrecognized".
    +const char REC_PLUGIN_CONFIG_NAME_PREFIX[] = "proxy.config.plugin.";
    +static const size_t REC_PLUGIN_CONFIG_NAME_PREFIX_LEN = 
sizeof(REC_PLUGIN_CONFIG_NAME_PREFIX)-1;
    --- End diff --
    
    You can't get the value of the record unless it is registered, so I don't 
think this saves you any work.


Issue Time Tracking
-------------------

    Worklog Id:     (was: 28535)
    Time Spent: 2h 40m  (was: 2.5h)

> ATS doesn't warn about unknown config items
> -------------------------------------------
>
>                 Key: TS-1882
>                 URL: https://issues.apache.org/jira/browse/TS-1882
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Configuration
>            Reporter: Ebrahim Mohammadi
>            Assignee: Alan M. Carroll
>             Fix For: 7.0.0
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Apache Traffic Server doesn't warn about unknown configuration file items. It 
> can cause huge confusions, specially in case of trying to get features of a 
> newer version to work on an older installed version by mistake, as I found 
> out the hard way!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to