510 NOT EXTENDED

The arrangement for getting to the asset has not been met in the request. The server ought to send back all the data fundamental for

Read More »

508 LOOP DETECTED

The server ended an activity since it experienced an unbounded circle while handling a request with “Profundity: unendingness”. This status demonstrates that the whole activity

Read More »

507 INSUFFICIENT STORAGE

The strategy couldn’t be performed on the asset in light of the fact that the server can’t store the representation expected to effectively finish the

Read More »

506 VARIANT ALSO NEGOTIATES

The server has an inward design mistake: the picked variation asset is arranged to participate in straightforward substance exchange itself, and is in this manner

Read More »

504 GATEWAY TIMEOUT

The server, while going about as a passage or intermediary, didn’t get an opportune reaction from an upstream server it expected to access so as

Read More »

503 SERVICE UNAVAILABLE

The server is presently incapable to deal with the request because of an impermanent over-burden or booked support, which will probably be reduced after some

Read More »

502 BAD GATEWAY

The server, while going about as a portal or intermediary, got an invalid reaction from an inbound server it got to while endeavoring to satisfy

Read More »

501 NOT IMPLEMENTED

The server doesn’t bolster the usefulness required to satisfy the request.  This is the proper reaction when the server doesn’t perceive the request strategy and

Read More »

499 CLIENT CLOSED REQUEST

A non-standard status code presented by nginx for the situation when a customer shuts the association while nginx is preparing the request. 

Read More »

426 UPGRADE REQUIRED

The server won’t play out the request utilizing the present convention however may be happy to do as such after the customer moves up to

Read More »

424 FAILED DEPENDENCY

The technique couldn’t be performed on the asset on the grounds that the mentioned activity relied upon another activity and that activity fizzled.  For instance,

Read More »

423 LOCKED

The source or goal asset of a technique is bolted.  This reaction SHOULD contain a suitable precondition or postcondition code, for example, ‘lock-token-submitted’ or ‘no-clashing

Read More »

422 UNPROCESSABLE ENTITY

The server comprehends the substance sort of the request element (henceforth a 415 Unsupported Media Type status code is improper), and the linguistic structure of

Read More »

421 MISDIRECTED REQUEST

The request was aimed at a server that can’t create a reaction. This can be sent by a server that isn’t arranged to deliver reactions

Read More »

417 EXPECTATION FAILED

The desire given in the request’s Expect header field1 couldn’t be met by at any rate one of the inbound servers.  418 I’M A TEAPOT 

Read More »

414 REQUEST-URI TOO LONG

The server is declining to support the request on the grounds that the request target is longer than the server is eager to decipher.  This

Read More »

413 PAYLOAD TOO LARGE

The server is declining to process a request on the grounds that the request payload is bigger than the server is willing or ready to

Read More »

412 PRECONDITION FAILED

At least one conditions given in the request header fields assessed to bogus when tried on the server.  This reaction code enables the customer to

Read More »

411 LENGTH REQUIRED

The server will not acknowledge the request without a characterized Content-Length.  The customer MAY rehash the request on the off chance that it includes a

Read More »

410 GONE

The objective asset is never again accessible at the cause server and that this condition is probably going to be lasting.  On the off chance

Read More »

409 CONFLICT

The request couldn’t be finished because of a contention with the present condition of the objective asset. This code is utilized in circumstances where the

Read More »

408 REQUEST TIMEOUT

The server didn’t get a total request message inside the time that it was set up to pause.  A server SHOULD send the “nearby” association

Read More »

406 NOT ACCEPTABLE

The objective asset doesn’t have a present representation that would be worthy to the client specialist, as per the proactive exchange header fields got in

Read More »

405 METHOD NOT ALLOWED

The strategy got in the request line is known by the source server however not upheld by the objective asset.  The starting point server MUST

Read More »

404 NOT FOUND

The starting point server didn’t locate a present representation for the objective asset or isn’t happy to unveil that one exists.  A 404 status code

Read More »

403 FORBIDDEN

The server comprehended the request however will not approve it.  A server that desires to make open why the request has been taboo can portray

Read More »

401 UNAUTHORIZED

The request has not been applied in light of the fact that it needs substantial verification accreditations for the objective asset.  The server producing a

Read More »

308 PERMANENT REDIRECT

The objective asset has been relegated another lasting URI and any future references to this asset should utilize one of the encased URIs.  Customers with

Read More »

305 USE PROXY

Characterized in a past form of this detail and is currently censured, because of security concerns with respect to in-band arrangement of an intermediary. 

Read More »

304 NOT MODIFIED

A restrictive GET or HEAD demand has been gotten and would have brought about a 200 OK reaction on the off chance that it were

Read More »

303 SEE OTHER

The server is diverting the client operator to an alternate asset, as showed by a URI in the Location header field, which is planned to

Read More »

302 FOUND

The objective asset lives incidentally under an alternate URI. Since the redirection may be adjusted now and again, the customer should keep on utilizing the

Read More »

301 MOVED PERMANENTLY

The objective asset has been allocated another lasting URI and any future references to this asset should utilize one of the encased URIs.  Customers with

Read More »

226 IM USED

The server has satisfied a GET demand for the asset, and the reaction is a representation of the consequence of at least one case controls

Read More »

208 ALREADY REPORTED

Utilized inside a DAV: propstat reaction component to abstain from identifying the inner individuals from different ties to a similar assortment over and again.  For

Read More »

207 MULTI-STATUS

A Multi-Status reaction passes on data about various assets in circumstances where numerous status codes may be proper.  The default Multi-Status reaction body is a

Read More »

206 PARTIAL CONTENT

The server is effectively satisfying a range demand for the objective asset by moving at least one pieces of the chose representation that relate to

Read More »

205 RESET CONTENT

The server has satisfied the requestand wants that the client operator reset the “report see”, which made the request be sent, to its unique state

Read More »

204 NO CONTENT

The server has effectively satisfied the request and that there is no extra content to send in the reaction payload body.  Metadata in the reaction

Read More »

202 ACCEPTED

202 ACCEPTED The request has been acknowledged for preparing, yet the handling has not been finished. The request may or may not in the end

Read More »

201 CREATED

The request has been satisfied and has brought about at least one new resource being made.  The essential resource made by the request is recognized

Read More »

200 OK

This sort of codes delineates that the request has succeeded. The payload sent in a 200 reaction depends upon the request technique. For the systems

Read More »

101 SWITCHING PROTOCOLS

This reaction code shows convention the server is understanding the requests and changing to as mentioned by a customer which sent the message including the

Read More »