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
Add global HTTP header rules #3788
Comments
@fabiocav Can we discuss prioritization here? There are a couple of scenarios where this would be useful, and it's blocking for some customers. We can discuss the details offline. |
kashimiz
added a commit
to kashimiz/azure-functions-host
that referenced
this issue
Jun 19, 2019
kashimiz
added a commit
to kashimiz/azure-functions-host
that referenced
this issue
Jul 16, 2019
kashimiz
added a commit
to kashimiz/azure-functions-host
that referenced
this issue
Jul 22, 2019
kashimiz
added a commit
to kashimiz/azure-functions-host
that referenced
this issue
Jul 26, 2019
kashimiz
added a commit
that referenced
this issue
Jul 26, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It might be nice to have host config that applies to responses for all HTTP endpoints. For example, while I can set headers from code for things like
X-Content-Type-Options: nosniff
, it would be nice to just define this once. This could be as simple as a quick dictionary in host.json.The text was updated successfully, but these errors were encountered: