Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

HttpStatusCode Enumeration

Contains the values of status codes defined for HTTP.

Namespace:  System.Net
Assembly:  System.Net (in System.Net.dll)
public enum HttpStatusCode
Member nameDescription
Supported by Silverlight for Windows PhoneContinueEquivalent to HTTP status 100. Continue indicates that the client can continue with its request.
Supported by Silverlight for Windows PhoneSwitchingProtocolsEquivalent to HTTP status 101. SwitchingProtocols indicates that the protocol version or protocol is being changed.
Supported by Silverlight for Windows PhoneOKEquivalent to HTTP status 200. OK indicates that the request succeeded and that the requested information is in the response. This is the most common status code to receive.
Supported by Silverlight for Windows PhoneCreatedEquivalent to HTTP status 201. Created indicates that the request resulted in a new resource created before the response was sent.
Supported by Silverlight for Windows PhoneAcceptedEquivalent to HTTP status 202. Accepted indicates that the request has been accepted for further processing.
Supported by Silverlight for Windows PhoneNonAuthoritativeInformationEquivalent to HTTP status 203. NonAuthoritativeInformation indicates that the returned metadata information is from a cached copy instead of the origin server and therefore may be incorrect.
Supported by Silverlight for Windows PhoneNoContentEquivalent to HTTP status 204. NoContent indicates that the request has been successfully processed and that the response is intentionally blank.
Supported by Silverlight for Windows PhoneResetContentEquivalent to HTTP status 205. ResetContent indicates that the client should reset (not reload) the current resource.
Supported by Silverlight for Windows PhonePartialContentEquivalent to HTTP status 206. PartialContent indicates that the response is a partial response as requested by a GET request that includes a byte range.
Supported by Silverlight for Windows PhoneMultipleChoicesEquivalent to HTTP status 300. MultipleChoices indicates that the requested information has multiple representations. The default action is to treat this status as a redirect and follow the contents of the Location header associated with this response.

MultipleChoices is a synonym for Ambiguous.

Supported by Silverlight for Windows PhoneAmbiguousEquivalent to HTTP status 300. Ambiguous indicates that the requested information has multiple representations. The default action is to treat this status as a redirect and follow the contents of the Location header associated with this response.

Ambiguous is a synonym for MultipleChoices.

Supported by Silverlight for Windows PhoneMovedPermanentlyEquivalent to HTTP status 301. MovedPermanently indicates that the requested information has been moved to the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response.

MovedPermanently is a synonym for Moved.

Supported by Silverlight for Windows PhoneMovedEquivalent to HTTP status 301. Moved indicates that the requested information has been moved to the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will use the GET method.

Moved is a synonym for MovedPermanently.

Supported by Silverlight for Windows PhoneFoundEquivalent to HTTP status 302. Found indicates that the requested information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will use the GET method.

Found is a synonym for Redirect.

Supported by Silverlight for Windows PhoneRedirectEquivalent to HTTP status 302. Redirect indicates that the requested information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will use the GET method.

Redirect is a synonym for Found.

Supported by Silverlight for Windows PhoneSeeOtherEquivalent to HTTP status 303. SeeOther automatically redirects the client to the URI specified in the Location header as the result of a POST. The request to the resource specified by the Location header will be made with a GET.

SeeOther is a synonym for RedirectMethod.

Supported by Silverlight for Windows PhoneRedirectMethodEquivalent to HTTP status 303. RedirectMethod automatically redirects the client to the URI specified in the Location header as the result of a POST. The request to the resource specified by the Location header will be made with a GET.

RedirectMethod is a synonym for SeeOther.

Supported by Silverlight for Windows PhoneNotModifiedEquivalent to HTTP status 304. NotModified indicates that the client's cached copy is up to date. The contents of the resource are not transferred.
Supported by Silverlight for Windows PhoneUseProxyEquivalent to HTTP status 305. UseProxy indicates that the request should use the proxy server at the URI specified in the Location header.
Supported by Silverlight for Windows PhoneUnusedEquivalent to HTTP status 306. Unused is a proposed extension to the HTTP/1.1 specification that is not fully specified.
Supported by Silverlight for Windows PhoneTemporaryRedirectEquivalent to HTTP status 307. TemporaryRedirect indicates that the request information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will also use the POST method.

TemporaryRedirect is a synonym for RedirectKeepVerb.

Supported by Silverlight for Windows PhoneRedirectKeepVerbEquivalent to HTTP status 307. RedirectKeepVerb indicates that the request information is located at the URI specified in the Location header. The default action when this status is received is to follow the Location header associated with the response. When the original request method was POST, the redirected request will also use the POST method.

RedirectKeepVerb is a synonym for TemporaryRedirect.

Supported by Silverlight for Windows PhoneBadRequestEquivalent to HTTP status 400. BadRequest indicates that the request could not be understood by the server. BadRequest is sent when no other error is applicable, or if the exact error is unknown or does not have its own error code.
Supported by Silverlight for Windows PhoneUnauthorizedEquivalent to HTTP status 401. Unauthorized indicates that the requested resource requires authentication. The WWW-Authenticate header contains the details of how to perform the authentication.
Supported by Silverlight for Windows PhonePaymentRequiredEquivalent to HTTP status 402. PaymentRequired is reserved for future use.
Supported by Silverlight for Windows PhoneForbiddenEquivalent to HTTP status 403. Forbidden indicates that the server refuses to fulfill the request.
Supported by Silverlight for Windows PhoneNotFoundEquivalent to HTTP status 404. NotFound indicates that the requested resource does not exist on the server.
Supported by Silverlight for Windows PhoneMethodNotAllowedEquivalent to HTTP status 405. MethodNotAllowed indicates that the request method (POST or GET) is not allowed on the requested resource.
Supported by Silverlight for Windows PhoneNotAcceptableEquivalent to HTTP status 406. NotAcceptable indicates that the client has indicated with Accept headers that it will not accept any of the available representations of the resource.
Supported by Silverlight for Windows PhoneProxyAuthenticationRequiredEquivalent to HTTP status 407. ProxyAuthenticationRequired indicates that the requested proxy requires authentication. The Proxy-authenticate header contains the details of how to perform the authentication.
Supported by Silverlight for Windows PhoneRequestTimeoutEquivalent to HTTP status 408. RequestTimeout indicates that the client did not send a request within the time the server was expecting the request.
Supported by Silverlight for Windows PhoneConflictEquivalent to HTTP status 409. Conflict indicates that the request could not be carried out because of a conflict on the server.
Supported by Silverlight for Windows PhoneGoneEquivalent to HTTP status 410. Gone indicates that the requested resource is no longer available.
Supported by Silverlight for Windows PhoneLengthRequiredEquivalent to HTTP status 411. LengthRequired indicates that the required Content-length header is missing.
Supported by Silverlight for Windows PhonePreconditionFailedEquivalent to HTTP status 412. PreconditionFailed indicates that a condition set for this request failed, and the request cannot be carried out. Conditions are set with conditional request headers like If-Match, If-None-Match, or If-Unmodified-Since.
Supported by Silverlight for Windows PhoneRequestEntityTooLargeEquivalent to HTTP status 413. RequestEntityTooLarge indicates that the request is too large for the server to process.
Supported by Silverlight for Windows PhoneRequestUriTooLongEquivalent to HTTP status 414. RequestUriTooLong indicates that the URI is too long.
Supported by Silverlight for Windows PhoneUnsupportedMediaTypeEquivalent to HTTP status 415. UnsupportedMediaType indicates that the request is an unsupported type.
Supported by Silverlight for Windows PhoneRequestedRangeNotSatisfiableEquivalent to HTTP status 416. RequestedRangeNotSatisfiable indicates that the range of data requested from the resource cannot be returned, either because the beginning of the range is before the beginning of the resource, or the end of the range is after the end of the resource.
Supported by Silverlight for Windows PhoneExpectationFailedEquivalent to HTTP status 417. ExpectationFailed indicates that an expectation given in an Expect header could not be met by the server.
Supported by Silverlight for Windows PhoneInternalServerErrorEquivalent to HTTP status 500. InternalServerError indicates that a generic error has occurred on the server.
Supported by Silverlight for Windows PhoneNotImplementedEquivalent to HTTP status 501. NotImplemented indicates that the server does not support the requested function.
Supported by Silverlight for Windows PhoneBadGatewayEquivalent to HTTP status 502. BadGateway indicates that an intermediate proxy server received a bad response from another proxy or the origin server.
Supported by Silverlight for Windows PhoneServiceUnavailableEquivalent to HTTP status 503. ServiceUnavailable indicates that the server is temporarily unavailable, usually due to high load or maintenance.
Supported by Silverlight for Windows PhoneGatewayTimeoutEquivalent to HTTP status 504. GatewayTimeout indicates that an intermediate proxy server timed out while waiting for a response from another proxy or the origin server.
Supported by Silverlight for Windows PhoneHttpVersionNotSupportedEquivalent to HTTP status 505. HttpVersionNotSupported indicates that the requested HTTP version is not supported by the server.

The HttpStatusCode enumeration contains the values of the status codes defined in RFC 2616 for HTTP 1.1 that are supported on Silverlight.

The status of an HTTP request is contained in the HttpWebResponse.StatusCode property.

The only status code values returned for the HTTP and HTTPS schemes are OK and NotFound.

Silverlight

Supported in: 5, 4, 3

Silverlight for Windows Phone

Supported in: Windows Phone OS 7.1, Windows Phone OS 7.0

XNA Framework

Supported in: Windows Phone OS 7.0

For a list of the operating systems and browsers that are supported by Silverlight, see Supported Operating Systems and Browsers.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.