Issue #7029
Accessing content for a distribution that is not assigned returns 404 which is confusing
Status:
NEW
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Today dkliban and I helped debug some 404 errors a user was hitting when trying to access their distribution through the content app. Turns out that distribution was not assigned to a publication. 404 is perhaps not the right error code (since the distribution exists) and also it would be more helpful to somehow alert the user that their distribution is not assigned.
History
#1
Updated by daviddavis 4 months ago
- Subject changed from Accessing a distribution that is not assigned is unhelpful to Accessing a distribution that is not assigned returns 404 which is confusing
#2
Updated by daviddavis 4 months ago
- Description updated (diff)
#3
Updated by daviddavis 4 months ago
- Subject changed from Accessing a distribution that is not assigned returns 404 which is confusing to Accessing content for a distribution that is not assigned returns 404 which is confusing
- Description updated (diff)
#4
Updated by dkliban@redhat.com 4 months ago
The server should return a 404 with an error message. E.g. 404: The distribution doesn't have a publication or repository version associated with it.
Please register to edit this issue
.