Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue/Help with "HTTP Response Codes" #773

Open
arunkpskpm opened this issue Nov 17, 2024 · 0 comments
Open

Issue/Help with "HTTP Response Codes" #773

arunkpskpm opened this issue Nov 17, 2024 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@arunkpskpm
Copy link

arunkpskpm commented Nov 17, 2024

Describe the problem

I'm exploring the provider-http Crossplane provider for our automation purposes and encountered an issue with Prisma Cloud's response codes. Specifically, Prisma Cloud returns a 400 status code for an invalid ID for GET
https://api.prismacloud.io/user/role/:id, where a 404 would be more appropriate according to standard response codes. Any possibilities to get it changed?

https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

400 Bad Request
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

404 Not Found
The server cannot find the requested resource. In the browser, this means the URL is not recognized. In an API, this can also mean that the endpoint is valid but the resource itself does not exist. Servers may also send this response instead of 403 Forbidden to hide the existence of a resource from an unauthorized client. This response code is probably the most well known due to its frequent occurrence on the web.

@arunkpskpm arunkpskpm added the documentation Improvements or additions to documentation label Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant