C# Class logv.http.ResponseExtensions

Appends a "private" to the Cache-Control header to deny caching on shared caches.

Appends a "public" to the Cache-Control header to allow public cache to cache the resource

Set the ETag header.

Gets the cached response that caches the data into a MemoryStream

Sets the max-age part of the Cache-Control header

Set the Cache-Control header to no-cache to enforce revalidation

Response with the status code: 201 Created The request has been fulfilled and resulted in a new resource being created.

Response with the status code: 202 Accepted The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place. You might add additional data to the response body for the client to check the state of the operation.

Response with the status code: 204 No Content The server successfully processed the request, but is not returning any content

Response with the status code: 204 No Content The server successfully processed the request, but is not returning any content

Response with the status code: 301 Moved Permanently This and all future requests should be directed to the given URI. The client normally will issue a GET request to that url not matter what the original request was.

Response with the status code: 303 See Other The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.

Response with the status code: 304 Not Modified Indicates the resource has not been modified since last requested. Typically, the HTTP client provides a header like the If-Modified-Since header to provide a time against which to compare. Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then sent again using more bandwidth of the server and client.

Response with the status code: 307 Temporary Redirect In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For instance, a POST request repeated using another POST request.

Response with the status code: 400 Bad Request The request cannot be fulfilled due to bad syntax.

Response with the status code: 401 Unauthorized Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.

Response with the status code: 403 Forbidden The request was a valid request, but the server is refusing to respond to it. Unlike a 401 Unauthorized response, authenticating will make no difference. On servers where authentication is required, this commonly means that the provided credentials were successfully authenticated but that the credentials still do not grant the client permission to access the resource (e.g. a recognized user attempting to access restricted content).

Response with the status code: 404 Not Found The requested resource could not be found but may be available again in the future. Subsequent requests by the client are permissible.

Response with the status code: 405 Method Not Allowed A request was made of a resource using a request method not supported by that resource; for example, using GET on a form which requires data to be presented via POST, or using PUT on a read-only resource.

Response with the status code: 409 Conflict Indicates that the request could not be processed because of conflict in the request, such as an edit conflict.

Response with the status code: 418 I'm a teapot (RFC 2324) This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers.

Response with the status code: 451 Unavailable For Legal Reasons (Internet draft) Defined in the internet draft "A New HTTP Status Code for Legally-restricted Resources". Intended to be used when resource access is denied for legal reasons, e.g. censorship or government-mandated blocked access. A reference to the 1953 dystopian novel Fahrenheit 451, where books are outlawed.

Response with the status code: 500 Internal Server Error A generic error message, given when no more specific message is suitable.

Response with the status code: 500 Internal Server Error A generic error message, given when no more specific message is suitable.

Response with the status code: 503 Service Unavailable The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

Response with the status code: 503 Service Unavailable The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

Response with the status code: 507 Insufficient Storage The server is unable to store the representation needed to complete the request

Serves the given file to the client and closes the request when done.

Serves the given file to the client and closes the request when done.

Writes the specified byte data to the response

Writes the given string to the response

Writes the given string to the response

Writes the given object to the response as JSON

Writes the given object to the response as JSON