Issue #7798
closed
Example Playbooks should configure content_origin with ssl in mind
Description
depending on pulp_webserver_disable_https the network protocol should be selected either http or https
Added by mdellweg over 3 years ago
Added by mdellweg over 3 years ago
Revision 7320aeee | View on GitHub
Use proper schema for content_origin in examples
Updated by mdellweg over 3 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset ansible-pulp|7320aeee52ff69a7878325cd050d0d47ad50cca0.
Updated by dalley over 3 years ago
(I know this wasn't introduced here, I just needed somewhere to start a discussion and I'm not sure if it's a real bug)
Is it necessary to explicitly include the protocol in the CONTENT_ORIGIN setting, or is it something we can backfill ourselves? The docs would suggest that it is supposed to be respected, but actually I don't think it is.
https://docs.pulpproject.org/pulpcore/settings.html?highlight=content_origin
A required string containing the protocol, fqdn, and port where the content app is reachable by users. This is used by pulpcore and various plugins when referring users to the content app. For example if the API should refer users to content at using http to pulp.example.com on port 24816, (the content default port), you would set: https://pulp.example.com:24816.
The "base_url" on Distributions is constructed using CONTENT_ORIGIN, which is supposedly where the content is available, but if CONTENT_ORIGIN uses http:// then the webserver will redirect to https://, which can cause problems if the client isn't expecting a redirect.
Updated by ttereshc about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Use proper schema for content_origin in examples
fixes #7798 https://pulp.plan.io/issues/7798