Statically setting CONTENT_ORIGIN is problematic in some cases
Consider the following cases:
- You don't control or know the public hostname your content app is being served at
- Your content app is being served by multiple hostnames
There are cases in which a sysadmin might not be able to statically set a CONTENT_ORIGIN. Pulp doesn't handle this at all.
Please register to edit this issue