You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: add cache-control header in the polling response
This header should not be needed since the client already includes a
cache busting query parameter ("t"), but a misconfigured CDN could
ignore the query parameters and cache the server response.
Related: socketio/socket.io#4842
"Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; Tablet PC 2.0)",
3467
3466
};
3468
-
testForHeaders(headers,done);
3467
+
testForHeaders(headers,(headers)=>{
3468
+
expect(headers["X-XSS-Protection"]).to.be("0");
3469
+
done();
3470
+
});
3469
3471
});
3470
3472
3471
3473
it("should contain X-XSS-Protection: 0 for IE11",(done)=>{
3472
3474
constheaders={
3473
3475
"user-agent":
3474
3476
"Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko",
3475
3477
};
3476
-
testForHeaders(headers,done);
3478
+
testForHeaders(headers,(headers)=>{
3479
+
expect(headers["X-XSS-Protection"]).to.be("0");
3480
+
done();
3481
+
});
3482
+
});
3483
+
3484
+
it("should include a 'cache-control' header",(done)=>{
0 commit comments