Why getting token from 'header' is more secure

1. Preventing Exposure in URLs: Tokens contained in the header are shielded from exposure in the URL. When URL parameters contain sensitive data, there may be a security issue because they are frequently recorded in multiple locations, including browser history and server logs.




2. Cross-Site Request Forgery (CSRF) Protection: Placing tokens in the header helps protect against CSRF attacks. Malicious websites may be able to operate on behalf of the user without authorization if tokens are present in the request body or …

backend browser cross-site cross-site request forgery csrf data exposure forgery header history issue logs may protection request security sensitive sensitive data server token tokens url urls webdev