Skip to content

Use CSRF headers#430

Merged
asfgit merged 5 commits intoapache:masterfrom
ahgittin:use-csrf-headers
Nov 16, 2016
Merged

Use CSRF headers#430
asfgit merged 5 commits intoapache:masterfrom
ahgittin:use-csrf-headers

Conversation

@ahgittin
Copy link
Copy Markdown
Contributor

Adds a filter which returns and requires special cookies/headers to protect against forged cross-site requests. Extensive documentation in CsrfTokenFilter. @neykov or @m4rkmckenna or @geomacy you might be best placed to check this.

Also small tidy to logout process in e9aecba -- would be useful if someone familiar with the thinking behind the existing process (switching to user) gives it a quick eyeball (probably @neykov or @bostko ?)

requesting such a header, and if required POST requests fail if it wasn't supplied
now supports AngularJS semantics.
also now it doesn't needlessly create sessions.
helps establish csrf protection. done in /server/user and /server/up/extended,
the two main places which an interactive app will hit early.
previously `curl /v1/logout` would throw 500 server error
@geomacy
Copy link
Copy Markdown
Contributor

geomacy commented Nov 16, 2016

To the best of my knowledge this looks good, from visual inspection and from test. (A malicious web page posting to the server got the 401 response generated by the CSRF filter.) +1

@asfgit asfgit merged commit 45686e4 into apache:master Nov 16, 2016
asfgit pushed a commit that referenced this pull request Nov 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants