Replies: 2 comments 1 reply
-
In our production instance of seqr the django admin does set the Origin header correctly. Are you sure this is an issue with the seqr app and not an issue with your proxy? |
Beta Was this translation helpful? Give feedback.
0 replies
-
You're correct, this was an issue with our proxy. Our proxy was setting the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello! I'm running seqr using docker compose behind a HAProxy instance, and I'm running into issues with submitting forms in the admin site. The admin site gives me 403 Forbidden errors as a response, and the seqr container logs show this error:
The browser sends
null
as the value for the HTTP "Origin" header, and I'm not sure how to correct this behaviour. This only seems to happen in the admin site; other POST requests within seqr correctly set the Origin header to the site's domain as expected (eg. adding/removing users from projects).I've checked this prior discussion and can confirm that my domain name is in the settings.py as expected. The problem is that POST requests from the admin site (
seqr.<domain>.com/admin/
) set the request Origin header asnull
for some reason.Please let me know if there's anything I can do to fix this, or if there's any additional information needed. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions