Jelle and I have been debugging over IRC, crossposting here for awareness
until I can get proper fixes pushed all the right places.
Jelle, like I, have "proper" enterprise deployments. I.e. SSL, galaxy under
a proxy-prefix, etc.
galaxy.ini:
1. galaxy_infrastructure_web_port = 8090
2. dyna
Hi jelle,
Replied to IRC but you disconnected.
- Do you have dynamic_proxy_external_proxy=True?
- You may need to set an Origin header, which is technically bad
practice, but since the user is validated by the galaxy cookie, it's a bit
more acceptable.
I'm on IRC for further debuggin
