|
You are here |
juffalow.com | ||
| | | | |
www.danieldemmel.me
|
|
| | | | | CORS can be tricky, especially if you need to do something beyond the basics like authorisation or custom headers | |
| | | | |
danielms.site
|
|
| | | | | I build things and drink coffee. | |
| | | | |
vanwilgenburg.wordpress.com
|
|
| | | | | On many projects CORS headers are configured incorrectly. Usually by putting some wildcards (*) in the config and things 'work'. In this article I will show how to create tests for the correct headers (using Karate, but it should be applicable to any test framework). Introduction CORS stands for Cross-Origin Resource Sharing. And that's pretty... | |
| | | | |
mathieu.fenniak.net
|
|
| | | Cross-site request forgery (CSRF) is a type of security exploit where a user's web browser is tricked by a third-party site into performing actions on websites that the user is logged into. It is often a difficult attack to pull off, as it requires a number of factors to line up at once. Protecting against it requires good discipline and good design practices, especially when it comes to protecting Web APIs. Here's a brief example of a fictitious CSRF attack against a bank: | ||