[
https://issues.apache.org/jira/browse/TS-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13946659#comment-13946659
]
Yunkai Zhang commented on TS-2636:
----------------------------------
Hi [~sudheerv]:
With LogFilter, the code needs to compare all fields in LogFormat:
1) to check if the field satisfy the <Condition = xxx>,
2) if Yes, to do WIPE.
It'll slow down each HTTP response, especially when the number of filters
become larger.
But with field-function, the WIPE action will only affect certain fields that
surrounding with %<WIPE(...)> function in LogFormat.
I can image that to implement a field-function would be more easier than adding
a new filter-action(with few codes), so don't worry, just try it:)
I'm pleasure to give you help if you need.
> 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)
