We managed to reproduce the problem in a matter that could explain why it's hanging.
Our public APIs are hosted behind HAProxy (and a firewall) which performs SSL termination.
With GET /v2 (on a SSL URL), the request gets redirect to a non-SSL URL (with the trailing slash added). However, as we do not expose in any way a non-SSL endpoint, this means our firewall will just drop any connection on tcp/80 port leaving the client hanging indefinitely.
Is there a way for nova-api to detect an upstream SSL termination and change the redirect URL accordingly?
We managed to reproduce the problem in a matter that could explain why it's hanging.
Our public APIs are hosted behind HAProxy (and a firewall) which performs SSL termination.
With GET /v2 (on a SSL URL), the request gets redirect to a non-SSL URL (with the trailing slash added). However, as we do not expose in any way a non-SSL endpoint, this means our firewall will just drop any connection on tcp/80 port leaving the client hanging indefinitely.
Is there a way for nova-api to detect an upstream SSL termination and change the redirect URL accordingly?