Skip to content

GPS-976: add forwarded-allow-ips for correct proxy behaviour #16

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.

Sign up for GitHub

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

Merged
KeeTraxx merged 1 commit into from
Sep 9, 2026
Merged

GPS-976: add forwarded-allow-ips for correct proxy behaviour #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,4 +78,11 @@ EXPOSE 8000

# Here we use uvicorn directly in order to configure its logging configuration file
# This can be done by using the CMD arg during docker run.
ENTRYPOINT ["uvicorn", "app.main:app", "--proxy-headers", "--host", "0.0.0.0", "--loop", "uvloop", "--http", "httptools"]
#
# --proxy-headers alone is not enough: it only enables the middleware, while
# --forwarded-allow-ips declares which peers may set X-Forwarded-*. It defaults to
# 127.0.0.1, but behind the ALB the peer is the load balancer's private IP, so the
# default silently drops X-Forwarded-Proto and every generated URL comes out as http.
# '*' is safe only because the task's security group accepts traffic from the ALB
# security group only; if that ever changes, pin the VPC CIDR here instead.
ENTRYPOINT ["uvicorn", "app.main:app", "--proxy-headers", "--forwarded-allow-ips", "*", "--host", "0.0.0.0", "--loop", "uvloop", "--http", "httptools"]