[
https://issues.apache.org/jira/browse/RANGER-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1309:
----------------------------------------
Attachment: 0001-RANGER-1309-Check-for-header-first-in-RangerCSRFPrev.patch
> Check for header first in RangerCSRFPreventionFilter
> ----------------------------------------------------
>
> Key: RANGER-1309
> URL: https://issues.apache.org/jira/browse/RANGER-1309
> Project: Ranger
> Issue Type: Improvement
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Priority: Trivial
> Fix For: 0.7.0
>
> Attachments:
> 0001-RANGER-1309-Check-for-header-first-in-RangerCSRFPrev.patch
>
>
> In the RangerCSRFPreventionFilter, we should check to see if the required
> header is present first, for efficiency reasons. Right now we check the user
> agent first, which involves a call to matcher.matches() on each of the
> (default) browser user agent Strings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
