We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According http://nginx.org/en/docs/http/ngx_http_headers_module.html there's an option named always that always returns the header field regardless of the response code.
always
It is useful particularly on cors headers.
Do you think it worst it to add a new annotation like annotationCorsAlways in order to define a variable like $cors.CorsAlways = "" or "always"
annotationCorsAlways
$cors.CorsAlways = "" or "always"
Example :
add_header 'Access-Control-Allow-Origin' '{{ $cors.CorsAllowOrigin }} {{ $cors.CorsAlways }}';
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
According http://nginx.org/en/docs/http/ngx_http_headers_module.html there's an option named
always
that always returns the header field regardless of the response code.It is useful particularly on cors headers.
Do you think it worst it to add a new annotation like
annotationCorsAlways
in order to define a variable like$cors.CorsAlways = "" or "always"
Example :
The text was updated successfully, but these errors were encountered: