Foreman » Installer

both pulp3 and pulp2 want to 'own' /pulp/content/ in their current apache configurations. In pulp2 /pulp/content was never used directly but the existing type specific paths (/pulp/iso, /pulp/repos) redirect to /pulp/content for pulp2.

Due to ordering issues, fetching pulp2 yum content via http:// works, but for https:// it tries to redirect to the pulpcore-content app instead of directing to pulp2.

my suggestion is to change /pulp/content within pulp2 to something else like /pulp2/content/. Since it is not user facing, we can change it to whatever we want.