5e8c966a40
currently it is impossible to use ironic-api for both internal and public api at the same time when both of those are using (ssl terminating) proxies as there's only one config option to override the resource url's in responses ([api]public_endpoint). This patch adds the http_proxy_to_wsgi middleware from oslo.middleware to the ironic API service, which, with properly configured proxies, makes the choice of correct URL automatic, and thus makes such scenario possible. As this middleware may potentially not properly handle some endpoint URL schemas, leave the api.public_endpoint option as a backup, but it will be ignored when proxy headers parsing is enabled. Change-Id: I3ce6b0726b479c2835f8777957b2cb12d8098aec Story: #2006303 Task: #36019
14 lines
517 B
YAML
14 lines
517 B
YAML
---
|
|
features:
|
|
- |
|
|
Ironic API service now supports HTTP proxy headers parsing
|
|
with the help of oslo.middleware package, enabled via new option
|
|
``[oslo_middleware]/enable_proxy_headers_parsing`` (``False`` by default).
|
|
|
|
This enables more complex setups of Ironic API service, for example when
|
|
the same service instance serves both internal and public API endpoints
|
|
via separate proxies.
|
|
|
|
When proxy headers parsing is enabled, the value of
|
|
``[api]/public_endpoint`` option is ignored.
|