Actions
Story #5727
closed
Statically setting CONTENT_ORIGIN is problematic in some cases
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
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.
Updated by daviddavis over 4 years ago
- Tracker changed from Issue to Story
- % Done set to 0
Updated by dkliban@redhat.com over 3 years ago
- Status changed from NEW to CLOSED - WONTFIX
Actions
.