docs: fix broken link to XSRF common protection mechanism (#40458)
PR Close #40458
This commit is contained in:
		
							parent
							
								
									fff9bd8fba
								
							
						
					
					
						commit
						b636406043
					
				| @ -995,7 +995,7 @@ consider moving it to a utility function or into the `PackageSearchService` itse | |||||||
| ## Security: XSRF protection | ## Security: XSRF protection | ||||||
| 
 | 
 | ||||||
| [Cross-Site Request Forgery (XSRF or CSRF)](https://en.wikipedia.org/wiki/Cross-site_request_forgery) is an attack technique by which the attacker can trick an authenticated user into unknowingly executing actions on your website. | [Cross-Site Request Forgery (XSRF or CSRF)](https://en.wikipedia.org/wiki/Cross-site_request_forgery) is an attack technique by which the attacker can trick an authenticated user into unknowingly executing actions on your website. | ||||||
| `HttpClient` supports a [common mechanism](https://en.wikipedia.org/wiki/Cross-site_request_forgery#Cookie-to-Header_Token) used to prevent XSRF attacks. | `HttpClient` supports a [common mechanism](https://en.wikipedia.org/wiki/Cross-site_request_forgery#Cookie-to-header_token) used to prevent XSRF attacks. | ||||||
| When performing HTTP requests, an interceptor reads a token from a cookie, by default `XSRF-TOKEN`, and sets it as an HTTP header, `X-XSRF-TOKEN`. | When performing HTTP requests, an interceptor reads a token from a cookie, by default `XSRF-TOKEN`, and sets it as an HTTP header, `X-XSRF-TOKEN`. | ||||||
| Since only code that runs on your domain could read the cookie, the backend can be certain that the HTTP request came from your client application and not an attacker. | Since only code that runs on your domain could read the cookie, the backend can be certain that the HTTP request came from your client application and not an attacker. | ||||||
| 
 | 
 | ||||||
|  | |||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user