You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: