-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
2.5
-
False
-
-
False
-
Moderate
Description
NGINX has a specific way in how it handles `add_header` configurations. According to the documentation, if an `add_header` config is added to the `location` block, then it will not inherit the other `add_header` configs that are a part of the `server` or `http` blocks.
Steps to Reproduce
- Create a variable file called `vars.yml` with the following content
--- nginx_user_http_config: - add_header X-RANDOM-HEADER "WALDO";
- Re-run the installer against your Ansible Automation Platform environment
./setup.sh -i inventory -- -b -e @vars.yml
- Go to the login and inspect the request via web developer tools
- See that some requests will have `X-RANDOM-HEADER` and others don't. Example would be the request to `/overview` will not show the header.
Actual Behavior
Header is not present in the request.
Expected Behavior
If customer's are to use various nginx settings within the Ansible Automation Platform installer, they will make the assumption that the header will be present. There are some sections where we are not able to add `add_header` such as the `location /` block. The installer only allows for setting NGINX settings at the `http` or `server` blocks.
Additional Context
N/A