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
Is your feature request related to a problem? Please describe.
It's common to configure security headers in API endpoints. See: https://github.com/helmetjs/helmet. We needed to configure this manually in most of our projects after we got a penetration testing report.
The one that always come back to us is: 'Strict-Transport-Security': 'max-age=.....; includeSubdomains;'
Describe the solution you'd like
Something like this:
constadapterApi=require("@laconia/adapter-api");constapigateway=adapterApi.apigateway({responseSecurityHeaders: true// Should `true` be default? Is this a breaking change?})exports.handler=laconia(apigateway(app)).register(instances);
In our first iteration, we can support only all the sensible defaults, and support customisation in the next iteration like:
Is your feature request related to a problem? Please describe.
It's common to configure security headers in API endpoints. See: https://github.com/helmetjs/helmet. We needed to configure this manually in most of our projects after we got a penetration testing report.
The one that always come back to us is:
'Strict-Transport-Security': 'max-age=.....; includeSubdomains;'
Describe the solution you'd like
Something like this:
In our first iteration, we can support only all the sensible defaults, and support customisation in the next iteration like:
See middy middleware for better inspiration too: https://github.com/middyjs/middy/blob/master/docs/middlewares.md#httpsecurityheaders
The text was updated successfully, but these errors were encountered: