Project

Profile

Help

Story #5727

Statically setting CONTENT_ORIGIN is problematic in some cases

Added by daviddavis 24 days ago. Updated 19 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

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.

History

#1 Updated by daviddavis 19 days ago

  • Tracker changed from Issue to Story
  • % Done set to 0

Please register to edit this issue

Also available in: Atom PDF