Issue #3846: Wrong status code - Pulp

Actions

Send by e-mail Copy link

Issue #3846

closed

Wrong status code

Added by vdusek over 6 years ago. Updated over 4 years ago.

Status:

CLOSED - WONTFIX

Priority:

Normal

Assignee:

vdusek

Category:

Sprint/Milestone:

3.0.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 42

Quarter:

Description

When I want to create a repository with a name which is already used for another repository, it returns status code 400 - Bad Request. According to this topic HTTP response code for POST when resource already exists I would suggest use 409 - Conflict.

Actions

Copy link

Updated by CodeHeeler over 6 years ago

Triaged changed from No to Yes
Sprint set to Sprint 39

Actions

Copy link

Updated by daviddavis over 6 years ago

FYI, there are a bunch of other models that have similar unique constraints: publishers, remotes, exporters, distributions, users, artifacts.

Actions

Copy link

Updated by vdusek over 6 years ago

According to the django-rest-framework issue tracker on Github (4509, 5385, ...) it looks like we're not the first to deal with this problem. If I understand it right, collaborators don't have any interest in tackling it themselves or their point of view is that 400 is OK for uniqueness constraints. So I guess we'll have to deal with it by implementing our own subclass of ApiException.

Actions

Copy link