[
https://issues.apache.org/jira/browse/RANGER-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910012#comment-17910012
]
Dineshkumar Yadav commented on RANGER-5089:
-------------------------------------------
Apache master :
https://github.com/apache/ranger/commit/8a605be505a03a8b692dfea02905cda9eac63c70
Apache ranger-2.6 :
https://github.com/apache/ranger/commit/a632997681b85ab635d3b471d1a0002c47466a17
> Getting 204 instead of 404 status code when invalid service name is passed
> --------------------------------------------------------------------------
>
> Key: RANGER-5089
> URL: https://issues.apache.org/jira/browse/RANGER-5089
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 3.0.0, 2.6.0
> Reporter: Rakesh Gupta
> Assignee: Rakesh Gupta
> Priority: Major
> Fix For: 3.0.0, 2.6.0
>
>
> The API /service/xusers/secure/download/\{invalid_service} returns a 204 No
> Content status for invalid service names, instead of the expected 404 Not
> Found.
> *CURRENT BEHAVIOR:*
> The API /service/xusers/secure/download/\{invalid_service} returns a 204 No
> Content status even when the service name is invalid or does not exist.
> *EXPECTED BEHAVIOR:*
> The API should return a 404 Not Found status when the provided service name
> is invalid or does not exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
