Document how to serve http vs https content
Document how users can serve content over both http and https using Pulp and a webserver. This involves having two prefixes (e.g.
/https/.../) for distribution base paths. Then the user sets up the webserver (nginx or apache or whatever) to server the content over http or https based on this prefix.
#3 Updated by daviddavis over 2 years ago
I think the last thing we decided on was to have two prefixes (e.g.
/https/.../) for distribution base paths. Then setting up the webserver (nginx or apache or whatever) to server the content over http or https based on this prefix. This is supported now and would just require some documentation.
I'm wondering if this is still the route we want to go?
#4 Updated by bmbouter over 2 years ago
daviddavis I think something like that is the only technical route I know of because Pulp can't be sure that http connections aren't actually being served via https instead. A path convention like this allows coordination between the sysadmin installing Pulp and the user using Pulp. +1 to documenting the convention as you've described it.
It's effectively a documentation-only feature since Pulp provides no special handling in this area. I like that because it allows environments which don't need both types (all https for example) to not have to think about it.
Please register to edit this issue