Skip to content

for delete failure case, respond with SC_CONFLICT rather than SC_METHOD_NOT_ALLOWED#802

Closed
Chenjp wants to merge 1 commit into
apache:mainfrom
Chenjp:delete_failure_sc
Closed

for delete failure case, respond with SC_CONFLICT rather than SC_METHOD_NOT_ALLOWED#802
Chenjp wants to merge 1 commit into
apache:mainfrom
Chenjp:delete_failure_sc

Conversation

@Chenjp

@Chenjp Chenjp commented Dec 18, 2024

Copy link
Copy Markdown
Contributor

Since allowed methods check has been performed previously, failure status code switch to 409 / SC_CONFLICT.

Root cause may be insufficient privileges, OS file locking, or already deleted by another concurrent request.

…OD_NOT_ALLOWED

Since allowed methods check has been performed previously, "method not allowed" is not suitable, then switch to 409.

Root cause may be insufficient privileges, OS file locking, or already deleted by another concurrent request.
@rmaucher

Copy link
Copy Markdown
Contributor

Changing things just for the sake of it is not a good plan. The return code is acceptable.

@rmaucher rmaucher closed this Dec 18, 2024
@Chenjp

Chenjp commented Dec 19, 2024

Copy link
Copy Markdown
Contributor Author

It’s confusing.
When clients send Options request later , delete method will still on the available table.

@Chenjp

Chenjp commented Dec 19, 2024

Copy link
Copy Markdown
Contributor Author

Changing things just for the sake of it is not a good plan. The return code is acceptable.

@rmaucher cause inconsistent allowed methods with Options results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants