HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 use.

Posted by Unknown 0 comments
In This this post am going to describe the  HTTP status codes that IIS 7.0, IIS 7.5, and IIS 8.0 use.

1xx - Informational

These HTTP status codes indicate a provisional response. The client computer receives one or more 1xx responses before the client computer receives a regular response. 

IIS 7.0, IIS 7.5, and IIS 8.0 use the following informational HTTP status codes:
  • 100 - Continue.
  • 101 - Switching protocols.

2xx - Success

These HTTP status codes indicate that the server successfully accepted the request. 

IIS 7.0, IIS 7.5, and IIS 8.0 use the following success HTTP status codes:
  • 200 - OK. The client request has succeeded.
  • 201 - Created.
  • 202 - Accepted.
  • 203 - Nonauthoritative information.
  • 204 - No content.
  • 205 - Reset content.
  • 206 - Partial content.

3xx - Redirection

These HTTP status codes indicate that the client browser must take more action to fulfill the request. For example, the client browser may have to request a different page on the server. Or, the client browser may have to repeat the request by using a proxy server. 

IIS 7.0, IIS 7.5, and IIS 8.0 use the following redirection HTTP status codes:
  • 301 - Moved permanently.
  • 302 - Object moved.
  • 304 - Not modified.
  • 307 - Temporary redirect.

4xx - Client error

These HTTP status codes indicate that an error occurred and that the client browser appears to be at fault. For example, the client browser may have requested a page that does not exist. Or, the client browser may not have provided valid authentication information. 

IIS 7.0, IIS 7.5, and IIS 8.0 use the following client error HTTP status codes:
  • 400 - Bad request. The request could not be understood by the server due to malformed syntax. The client should not repeat the request without modifications.

    IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 400 error: 
    • 400.1 - Invalid Destination Header.
    • 400.2 - Invalid Depth Header.
    • 400.3 - Invalid If Header.
    • 400.4 - Invalid Overwrite Header.
    • 400.5 - Invalid Translate Header.
    • 400.6 - Invalid Request Body.
    • 400.7 - Invalid Content Length.
    • 400.8 - Invalid Timeout.
    • 400.9 - Invalid Lock Token.
  • 401 - Access denied.

    IIS 7.0, IIS 7.5, and IIS 8.0 define several HTTP status codes that indicate a more specific cause of a 401 error. The following specific HTTP status codes are displayed in the client browser but are not displayed in the IIS log: 
    • 401.1 - Logon failed.
    • 401.2 - Logon failed due to server configuration.
    • 401.3 - Unauthorized due to ACL on resource.
    • 401.4 - Authorization failed by filter.
    • 401.5 - Authorization failed by ISAPI/CGI application.
  • 403 - Forbidden.

    IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 403 error: 
    • 403.1 - Execute access forbidden.
    • 403.2 - Read access forbidden.
    • 403.3 - Write access forbidden.
    • 403.4 - SSL required.
    • 403.5 - SSL 128 required.
    • 403.6 - IP address rejected.
    • 403.7 - Client certificate required.
    • 403.8 - Site access denied.
    • 403.9 - Forbidden: Too many clients are trying to connect to the web server.
    • 403.10 - Forbidden: web server is configured to deny Execute access.
    • 403.11 - Forbidden: Password has been changed.
    • 403.12 - Mapper denied access.
    • 403.13 - Client certificate revoked.
    • 403.14 - Directory listing denied.
    • 403.15 - Forbidden: Client access licenses have exceeded limits on the web server.
    • 403.16 - Client certificate is untrusted or invalid.
    • 403.17 - Client certificate has expired or is not yet valid.
    • 403.18 - Cannot execute requested URL in the current application pool.
    • 403.19 - Cannot execute CGI applications for the client in this application pool.
    • 403.20 - Forbidden: Passport logon failed.
    • 403.21 - Forbidden: Source access denied.
    • 403.22 - Forbidden: Infinite depth is denied.
    • 403.502 - Forbidden: Too many requests from the same client IP; Dynamic IP Restriction limit reached.
  • 404 - Not found.

    IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 404 error:
    • 404.0 - Not found.
    • 404.1 - Site Not Found.
    • 404.2 - ISAPI or CGI restriction.
    • 404.3 - MIME type restriction.
    • 404.4 - No handler configured.
    • 404.5 - Denied by request filtering configuration.
    • 404.6 - Verb denied.
    • 404.7 - File extension denied.
    • 404.8 - Hidden namespace.
    • 404.9 - File attribute hidden.
    • 404.10 - Request header too long.
    • 404.11 - Request contains double escape sequence.
    • 404.12 - Request contains high-bit characters.
    • 404.13 - Content length too large.
    • 404.14 - Request URL too long.
    • 404.15 - Query string too long.
    • 404.16 - DAV request sent to the static file handler.
    • 404.17 - Dynamic content mapped to the static file handler via a wildcard MIME mapping.
    • 404.18 - Querystring sequence denied.
    • 404.19 - Denied by filtering rule.
    • 404.20 - Too Many URL Segments
  • 405 - Method Not Allowed.
  • 406 - Client browser does not accept the MIME type of the requested page.
  • 408 - Request timed out.
  • 412 - Precondition failed.

5xx - Server error

These HTTP status codes indicate that the server cannot complete the request because the server encounters an error.

 IIS 7.0, IIS 7.5, and IIS 8.0 use the following server error HTTP status codes:
  • 500 - Internal server error.

    IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 500 error:
    • 500.0 - Module or ISAPI error occurred.
    • 500.11 - Application is shutting down on the web server.
    • 500.12 - Application is busy restarting on the web server.
    • 500.13 - Web server is too busy.
    • 500.15 - Direct requests for Global.asax are not allowed.
    • 500.19 - Configuration data is invalid.
    • 500.21 - Module not recognized.
    • 500.22 - An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
    • 500.23 - An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
    • 500.24 - An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
    • 500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
      Note Here is where the distributed rules configuration is read for both inbound and outbound rules.
    • 500.51 - A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
      Note Here is where the global rules configuration is read.
    • 500.52 - A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
    • 500.53 - A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
    • 500.100 - Internal ASP error.
  • 501 - Header values specify a configuration that is not implemented.
  • 502 - Web server received an invalid response while acting as a gateway or proxy.

    IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 502 error:
    • 502.1 - CGI application timeout.
    • 502.2 - Bad gateway: Premature Exit.
    • 502.3 - Bad Gateway: Forwarder Connection Error (ARR).
    • 502.4 - Bad Gateway: No Server (ARR).
  • 503 - Service unavailable.

    IIS 7.0, IIS 7.5, and IIS 8.0 define the following HTTP status codes that indicate a more specific cause of a 503 error:
    • 503.0 - Application pool unavailable.
    • 503.2 - Concurrent request limit exceeded.
    • 503.3 - ASP.NET queue full
Labels: ,

Managing Persistent User State in Your ASP.NET

Posted by Unknown 0 comments

Managing Persistent User State in Your ASP.NET

 In this post i want to give very simple  and clear information about state management  in asp.net.
ASP.net Provides different ways managing states between the user requests.
There are nine ways to manage state in asp.net those are
Here is simple differentiation between these nine state management ways
Persistence MethodWho Needs the Data?For How Long?How Much Data?
ApplicationAll usersUntil the next application restartCan be almost any size—it will only be stored once
CookieOne userAs short as desired, or for months or even years if the user doesn't delete their cookiesMinimal, simple data
Form PostOne userFor the next request (can be reused across many requests)Virtually any size—the data is sent back and forth with every page
QueryStringOne user or one group of usersFor the next request (can be reused across many requests)Minimal, simple data
SessionOne userAs long as the user is active, plus a timeout period (typically 20 minutes)Can be almost any size, but should be minimized since every user has their own separate session store
CacheAll users or a subset of usersAs long or as short as neededCan be used for large or small, simple or complex data
ContextOne userThis request onlyCan hold large objects, but typically does not since it is often used for every request 
ViewStateOne userOne Web formMinimal; as with Form Post, this data is sent back and forth with every page
Config fileAll usersUntil the configuration file is updatedCan hold a lot of data; usually organized as many small strings or XML structures
Hope this will helps you
Labels: , ,
Subscribe to: Posts (Atom)
 
test