我目前正在开发Angular4应用。现在我想实现XSRF保护。在Response头cookie中,我收到“XSRF-TOKEN”,我需要在下一个Request头cookie中发送“X-XSRF-TOKEN”。正如official Angular document中提到的,Angular正在处理这个问题。但就我而言,棱角分明没有处理它。所以我创建了以下自定义XsrfInterceptor来附加带响应头的“X-XSRF-TOKEN”。
import { NgModule, Injectable } from '@angular/core';
import { Observable } from "rxjs/Observable";
import { HttpRequest, HttpHandler, HttpEvent, HttpXsrfTokenExtractor, HttpInterceptor } from "@angular/common/http";
@Injectable()
export class XsrfInterceptor implements HttpInterceptor {
constructor(private tokenExtractor: HttpXsrfTokenExtractor) {
}
intercept(req: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> {
const headerName = 'X-XSRF-TOKEN';
console.log("xsrf intercepter called");
let requestToForward = req;
let token = this.tokenExtractor.getToken() as string;
console.log(token);
if (token !== null) {
requestToForward = req.clone({ setHeaders: {headerName: token } });
}
return next.handle(requestToForward);
}
}
在我的主要模块中,我将其包含在提供者中,
providers: [
LoginService,
AuthGuardLogin,
{ provide: HTTP_INTERCEPTORS, useClass: XsrfInterceptor, multi: true }
],
但不幸的是它没有用。我认为我的aopplication不是调用自定义Intercepter的拦截方法(它不是打印console.log('xsrf intercepter called'))。
我的http标题如下:
let httpHeader = new RequestOptions({
headers: new Headers({
'Content-Type': 'application/json',
'x-auth-token': this.authToken
})
})
回复标题:
Access-Control-Allow-Credentials:true
Access-Control-Allow-Headers:Access-Control-Allow-Origin, Access-Control-Allow-Headers, Accept, X-XSRF-TOKEN, XSRF-TOKEN, X-Requested-By, Content-Type, Origin, Authorization, X-Requested-With, x-auth-token, OPTIONS
Access-Control-Allow-Methods:POST, GET, PUT, OPTIONS
Access-Control-Allow-Origin:http://localhost:7070
Access-Control-Expose-Headers:x-auth-token, XSRF-TOKEN, X-XSRF-TOKEN
Access-Control-Max-Age:3600
Cache-Control:no-cache, no-store, max-age=0, must-revalidate
Date:Fri, 24 Nov 2017 06:42:20 GMT
Expires:0
Pragma:no-cache
Referrer-Policy:same-origin
Set-Cookie:XSRF-TOKEN=63f66e2a-1ad0-4641-8f36-27c16734a676;path=/mfleet;HttpOnly
Transfer-Encoding:chunked
x-auth-token:8d06b1da-c35b-42ea-ac28-eae51f3dd74d
X-Content-Type-Options:nosniff
X-Frame-Options:DENY
X-XSS-Protection:1; mode=block
下一个请求标题:
Accept:application/json, text/plain, */*
Accept-Encoding:gzip, deflate, br
Accept-Language:en-US,en;q=0.9
Connection:keep-alive
Content-Type:application/json
Cookie:XSRF-TOKEN=63f66e2a-1ad0-4641-8f36-27c16734a676 **//this should be X-XSRF-TOKEN**
Host:localhost:7070
Referer:http://localhost:7070/dist/
User-Agent:Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
x-auth-token:8d06b1da-c35b-42ea-ac28-eae51f3dd74d
我正在使用以下版本的角度库:
"@angular/animations": "^4.4.5",
"@angular/cdk": "^2.0.0-beta.8",
"@angular/common": "^4.0.0",
"@angular/compiler": "^4.0.0",
"@angular/core": "^4.0.0",
"@angular/forms": "^4.0.0",
"@angular/http": "4.0.0",
"@angular/material": "^2.0.0-beta.8",
"@angular/platform-browser": "^4.0.0",
"@angular/platform-browser-dynamic": "^4.0.0",
"@angular/router": "^4.0.0",
答案 0 :(得分:2)
只有在导入正确的模块时,Angular才会处理XSRF。并且只有4.3以后才实现新的http客户端和拦截器。
您应该将angular更新为至少4.3.0(我建议升级到5.0.0,因为最后一个版本的material2需要这个),然后在您的app模块中导入HttpClientXsrfModule。然后它应该开箱即用。
此致