-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP response headers from Azure Functions should align with OWASP best-practices #9636
Comments
Thanks for informing. pls refer updated document. |
@bhagyshricompany What updated document are you referring to? |
@bhagyshricompany If it's relevant, we need to do this on a NodeJS function app. |
Direct manipulation of the web.config file is generally not recommended for Azure Functions. |
@bhagyshricompany Understand that if we modify webconfig we might encounter problems. How do we even access the web config in a zip deployment? We use Azure DevOps to build and deploy. |
Any update? |
ping |
? |
@bhagyshricompany I updated the title to reflect the reason I asked about the web.config. Hopefully the new title and description are helpful in prioritizing this issue |
any thoughts? |
? |
Scope
This question applies to a Function App running on a Windows App Service Plan.
On AppServices, we're able to modify the
web.config
to update response headers to meet the OWASP Secure Headers recommendations. This is a corporate policy, and violdating it includes penalties "up to and including termination". I doubt anyone would actually be fired for this, but...Can we access the web.config file to do the same on Azure Functions?
The text was updated successfully, but these errors were encountered: