[jira] [Commented] (WICKET-6786) CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on WICKET-6786:
---------------------------------------------------------

Commit 61f4b93c31672065b56cce9382892406d9da5016 in wicket's branch refs/heads/master from Santiago
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=61f4b93 ]

WICKET-6786: Minor refactor of FetchMetadataRequestCycleListener.


> CsrfPreventionRequestCycleListener should support Fetch Metadata Request Headers
> --------------------------------------------------------------------------------
>
>                 Key: WICKET-6786
>                 URL: https://issues.apache.org/jira/browse/WICKET-6786
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-core
>    Affects Versions: 9.0.0-M5, 8.8.0
>            Reporter: Emond Papegaaij
>            Priority: Major
>
> {{CsrfPreventionRequestCycleListener}} tries to determine the origin of a request via interpretation of the origin header and use this to block cross origin requests. The origin header however is not very reliable. For example, when a user opens a link in a new tab, the header is not sent. Fetch Metadata Request Headers (https://w3c.github.io/webappsec-fetch-metadata/) aims to solve this via a set of well defined headers. For Wicket, {{sec-fetch-site}} is the most important: {{same-origin}} is safe, {{none}} is a user opening a link via (for example) a bookmark, {{same-site}} and {{cross-origin}} should be blocked.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)