[ 
https://issues.apache.org/jira/browse/TS-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13974324#comment-13974324
 ] 

Bryan Call edited comment on TS-2636 at 4/18/14 6:22 PM:
---------------------------------------------------------

I don't see how implementing this feature as a function or a filter makes a 
difference on performance.  They both would do the same thing.  It is more 
about how we would like the configuration to look more then the functionality.

I don't think there is a clean way to specify what to wipe/clear that would 
make this generic for more then just being able to be used for fields.

I think implementing it as a filter is easier to understand when multiple field 
values that need to be wiped/cleared.

Maybe the action should be changed to WIPE_FIELD_VALUE to be more explicit 
about what it is doing.



was (Author: bcall):
I don't see how implementing this feature as a function or a filter makes a 
difference on performance.  They both would do the same thing.  It is more 
about how we would like the configuration to look more then the functionality.

I don't think there is a clean way to specify what to wipe/clear that would 
make this generic for more then just being able to be used for fields.

Maybe the action should be changed to WIPE_FIELD_VALUE to be more explicit 
about what it is doing.

> Enhance ATS custom logging to support WIPE filter action
> --------------------------------------------------------
>
>                 Key: TS-2636
>                 URL: https://issues.apache.org/jira/browse/TS-2636
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Logging
>            Reporter: Sudheer Vinukonda
>            Assignee: Yunkai Zhang
>              Labels: Review
>             Fix For: 5.0.0
>
>         Attachments: ts2636.diff
>
>
> Currently, ATS custom logging supports LogFilters with actions Accept, 
> Reject. This feature request is to add a new filter action "WIPE". WIPE can 
> be used in hiding sensitive parameters (e.g. userid, password) within the 
> query part of a URL. Attached is a draft version of the patch. Kindly review 
> and comment. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to