blob: f60ce766b2bc03dce3c8b5d576fbe53b12ccc075 [file] [log] [blame]
Ed Tanous8041f312017-04-03 09:47:01 -07001#pragma once
2
Ed Tanousc94ad492019-10-10 15:39:33 -07003#include <http_request.h>
4#include <http_response.h>
Ed Tanous8041f312017-04-03 09:47:01 -07005
Ed Tanous1abe55e2018-09-05 08:30:59 -07006namespace crow
7{
Ed Tanous1abe55e2018-09-05 08:30:59 -07008struct SecurityHeadersMiddleware
9{
10 struct Context
11 {
12 };
Ed Tanous8041f312017-04-03 09:47:01 -070013
Ed Tanous1abe55e2018-09-05 08:30:59 -070014 void beforeHandle(crow::Request& req, Response& res, Context& ctx)
15 {
Ed Tanousfd828ba2018-08-09 10:58:08 -070016#ifdef BMCWEB_INSECURE_DISABLE_XSS_PREVENTION
Ed Tanous1abe55e2018-09-05 08:30:59 -070017 if ("OPTIONS"_method == req.method())
18 {
19 res.end();
20 }
21#endif
Ed Tanousfd828ba2018-08-09 10:58:08 -070022 }
Ed Tanous8041f312017-04-03 09:47:01 -070023
Ed Tanous1abe55e2018-09-05 08:30:59 -070024 void afterHandle(Request& req, Response& res, Context& ctx)
25 {
26 /*
27 TODO(ed) these should really check content types. for example,
28 X-UA-Compatible header doesn't make sense when retrieving a JSON or
29 javascript file. It doesn't hurt anything, it's just ugly.
30 */
Ed Tanous750ceae2018-11-30 15:02:22 -080031 using bf = boost::beast::http::field;
32 res.addHeader(bf::strict_transport_security, "max-age=31536000; "
33 "includeSubdomains; "
34 "preload");
35 res.addHeader(bf::x_frame_options, "DENY");
36
37 res.addHeader(bf::pragma, "no-cache");
38 res.addHeader(bf::cache_control, "no-Store,no-Cache");
Ed Tanous3eb2f352018-12-20 12:30:45 -080039
Ed Tanousa3268f92019-09-23 14:06:03 -070040 res.addHeader("X-XSS-Protection", "1; "
41 "mode=block");
42 res.addHeader("X-Content-Type-Options", "nosniff");
43
44#ifndef BMCWEB_INSECURE_DISABLE_XSS_PREVENTION
Ed Tanouse6de21a2019-08-21 12:50:42 -070045 res.addHeader("Content-Security-Policy", "default-src 'none'; "
46 "img-src 'self' data:; "
47 "font-src 'self'; "
48 "style-src 'self'; "
49 "script-src 'self'; "
50 "connect-src 'self' wss:");
51 // The KVM currently needs to load images from base64 encoded
52 // strings. img-src 'self' data: is used to allow that.
Ed Tanous3eb2f352018-12-20 12:30:45 -080053 // https://stackoverflow.com/questions/18447970/content-security-policy-data-not-working-for-base64-images-in-chrome-28
Ed Tanouse6de21a2019-08-21 12:50:42 -070054
Ed Tanousa3268f92019-09-23 14:06:03 -070055#else
56 // If XSS is disabled, we need to allow loading from addresses other
57 // than self, as the BMC will be hosted elsewhere.
58 res.addHeader("Content-Security-Policy", "default-src 'none'; "
59 "img-src *; "
60 "font-src *; "
61 "style-src *; "
62 "script-src *; "
63 "connect-src *");
Ed Tanousfd828ba2018-08-09 10:58:08 -070064
Ed Tanousa3268f92019-09-23 14:06:03 -070065 const std::string_view origin = req.getHeaderValue("Origin");
66 res.addHeader(bf::access_control_allow_origin, origin);
Ed Tanous750ceae2018-11-30 15:02:22 -080067 res.addHeader(bf::access_control_allow_methods, "GET, "
68 "POST, "
69 "PUT, "
Ed Tanousda7f41e2018-12-10 13:36:40 -080070 "PATCH, "
71 "DELETE");
Ed Tanous750ceae2018-11-30 15:02:22 -080072 res.addHeader(bf::access_control_allow_credentials, "true");
73 res.addHeader(bf::access_control_allow_headers, "Origin, "
74 "Content-Type, "
75 "Accept, "
76 "Cookie, "
77 "X-XSRF-TOKEN");
Ed Tanousfd828ba2018-08-09 10:58:08 -070078
79#endif
Ed Tanous1abe55e2018-09-05 08:30:59 -070080 }
Ed Tanous8041f312017-04-03 09:47:01 -070081};
Ed Tanous1abe55e2018-09-05 08:30:59 -070082} // namespace crow