WaspHttpStatusCodes

It is a standard response for successful HTTP requests (HttpStatusCode.OK = 200).

Indicates that the request is successfully processed, but there is no content to return back to the client. (HttpStatusCode.NoContent = 204)

The WaspResult messages with this status are SUCCESS WITH WARNING messages HttpStatus Code 207: 207 Multi-Status — or action was ambiguous but successful- The consumer should decide if it is good or bad and how to proceed further.

Indicates that the request has more than one possible responses.

Indicates WaspResult messages with this status was successfully processed but messages contain errors. The consumer should decide if it is good or bad and how to proceed further. FYI: We can't return HTTP errors level 400 and up for errors otherwise the proxy can not process the result.

( HttpStatusCode.BadRequest = 400 )

Equivalent to HTTP status 410. System.Net.HttpStatusCode. Gone indicates that the requested resource is no longer available. Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices.[40] Most use cases do not require clients and search engines to purge the resource, and a ''404 Not Found'' may be used instead.

Error: the data provided from the client has an error (logical error, improperly formed, etc.. )

Error: the server had an error processing the request. ( HttpStatusCode.InternalServerError = 500 )

( HttpStatusCode.Forbidden = 403 )

( HttpStatusCode.NotFound = 404 )

( HttpStatusCode.UpgradeRequired = 426 ( eg 0x1aa in hexadecimal ) returned when the licenses has expired