| Name |
Last commit
|
Last update |
|---|---|---|
| .wiki-images | ||
| cloud_migrations | ||
| cloudformation_templates | ||
| doc | ||
| git-hooks | ||
| playbooks | ||
| util | ||
| vagrant | ||
| .gitignore | ||
| .travis.yml | ||
| AUTHORS | ||
| CHANGELOG.md | ||
| LICENSE.TXT | ||
| README.md | ||
| ec2_local_1.6.3 | ||
| requirements.txt |
The nginx configuration was set to pass X-Forwarded-For and related headers unodified to backend services. This works fine when nginx is deployed behind another load balancer (for example ELB), which already properly sets the X-Forwarded-* for headers. But in simpler deployment scenarios, where nginx is directly facing the end user, nginx should discard any existing X-Forwarded-For headr and set it to remote IP of the request, the X-Forwarded-Port header to the nginx server port, and the X-Forwarded-Proto to the scheme of the current request. The 'NGINX_SET_X_FORWARDED_HEADERS' is set to False by default, but set to True in the edx_sandbox playbook, where an additional load balancer in front of nginx is not usually present.
| Name |
Last commit
|
Last update |
|---|---|---|
| .wiki-images | Loading commit data... | |
| cloud_migrations | Loading commit data... | |
| cloudformation_templates | Loading commit data... | |
| doc | Loading commit data... | |
| git-hooks | Loading commit data... | |
| playbooks | Loading commit data... | |
| util | Loading commit data... | |
| vagrant | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| AUTHORS | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| LICENSE.TXT | Loading commit data... | |
| README.md | Loading commit data... | |
| ec2_local_1.6.3 | Loading commit data... | |
| requirements.txt | Loading commit data... |