100’s = informational status codes 200’s = success codes 300’s = redirection codes 400’s = client error codes 500’s = server error codes
Accepted - Often used for asynchronous processing. This code tells the client that the request was valid, but its processing will finish sometime in the future. The response body should include an URL to the finished resource with some information about when it will be available, or an URL to some monitoring endpoint that tells the client when the resource is available.
See Other - Like the 202 code but using a Location header field in response to informing the client about the location of the created resource or an endpoint that lets the client check for the status of the creation process. Some clients follow the status codes of the Redirect-class automatically. This code is usually only used for POST requests.
204 No Content
405
403 Forbidden - The client has authorized or doesn’t need to authorize itself, but still has no permissions to access the resource.
cause when we working on the code locally , we store the data as local environment variable and this add security
is software that lies between an operating system and the applications running on it. Essentially functioning as hidden translation layer, middleware enables communication and data management for distributed applications.
this set up the server to accept JSOn
whatever we passed after the first slash is and id
patch is only for update what the user pass(update whats given) , but put update all the info at once
in curly brackets we add the information for specific kay and value pair in a schema.
there has been an error on the server
201 is successful created object and its more specific. 200 mean everything was successful