PaloAltoNetworks / PaloAltoNetworks/pan.dev

Issue/Help with "HTTP Response Codes"

Open
#773 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
MDX
Stars
78
Forks
88
Avg merge
5d 17h
Merged PRs (30d)
18

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the Prisma Cloud GET /user/role/:id endpoint and its 400 response, but no repository file or test. Start by determining whether provider-http or Prisma Cloud owns the response behavior. Done would require an identified owner and an agreed resolution for invalid IDs.

Written by the indexing model from the issue text.

Assessment

Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.