Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Fix flower login if used behind a proxy via socket #3187
The login redirect uri was always using the port, even if flower is served
Run flower as:
example nginx snippet:
While this is nice, there is still one problem: If you use SSL, you'd need to use flower's unix socket with SSL too (which doesn't make much sense) because otherwise the
Maybe there is some way to get the current URL that was used to access the page? This would always work, regardless of what type of socket or protocol is used...
Yes the http/https problem is not fully solved ( In my install it works, as there is a redirect from http to https configured in nginx as well. I think the probably the easiest solution would be adding further settings in indico to override the computed redirect uri ( then passed as enviroment vars in the flower execution)