Skip to main content

Status codes from return from server

Http Response codes as specified in Servlet API (
Indicating the client can continue.
Indicating the server is switching protocols according to Upgrade header.
Indicating the request succeeded normally.
Indicating the request succeeded and created a new resource on the server.
Indicating that a request was accepted for processing, but was not completed.
Indicating that the meta information presented by the client did not originate from the server.
Indicating that the request succeeded but that there was no new information to return.
Indicating that the agent SHOULD reset the document view which caused the request to be sent.
Indicating that the server has fulfilled the partial GET request for the resource.
Indicating that the requested resource corresponds to any one of a set of representations, each with its own specific location.
Indicating that the resource has permanently moved to a new location, and that future references should use a new URI with their requests.
Indicating that the resource reside temporarily under a different URI.
Indicating that the response to the request can be found under a different URI.
Indicating that a conditional GET operation found that the resource was available and not modified.
Indicating that the requested resource MUST be accessed through the proxy given by the Location field.
Indicating that the requested resource resides temporarily under a different URI.
Indicating the request sent by the client was syntactically incorrect.
Indicating that the request requires HTTP authentication.
 Reserved for future use.
Indicating the server understood the request but refused to fulfill it.
Indicating that the requested resource is not available.
Indicating that the method specified in the Request-Line is not allowed for the resource identified by the Request-URI.(e.g. if Method is GET but there is no doGet() method)
Indicating that the resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
Indicating that the client MUST first authenticate itself with the proxy.
Indicating that the client did not produce a request within the time that the server was prepared to wait.
Indicating that the request could not be completed due to a conflict with the current state of the resource.
Indicating that the resource is no longer available at the server and no forwarding address is known.
Indicating that the request cannot be handled without a defined Content-Length.
Indicating that the precondition given in one or more of the request-header fields evaluated to false when it was tested on the server.
Indicating that the server is refusing to process the request because the request entity is larger than the server is willing or able to process.
Indicating that the server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.
Indicating that the server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
Indicating that the server cannot serve the requested byte range.
Indicating that the server could not meet the expectation given in the Expect request header.
Indicating an error inside the HTTP server which prevented it from fulfilling the request.
Indicating the HTTP server does not support the functionality needed to fulfill the request.
Indicating that the HTTP server received an invalid response from a server it consulted when acting as a proxy or gateway.
Indicating that the HTTP server is temporarily overloaded, and unable to handle the request.
Indicating that the server did not receive a timely response from the upstream server while acting as a gateway or proxy.
Indicating that the server does not support or refuses to support the HTTP protocol version that was used in the request message.


Popular posts from this blog

Using HyperSQL (HSQLDB)

HSQLDB is a portable RDBMS implemented in pure java. It can be embedded with your application as well as can be used separately. It is very a small database that supports almost all features of the standard database system. It comes with small jar file that can be found in lib folder. The HSQLDB jar package is located in the /lib directory of the ZIP package and contains several components and programs. Core components of jar file are : HyperSQL RDBMS Engine (HSQLDB), HyperSQL JDBC Driver, Database Manager, and Sql Tool. Installing and Using Download: download latest release of HyperSQL database from website and extract it. You will see following contents. Here "bin" directory contains some batch files those can be used to run a swing based GUI tool. You can use runManagerSwing.bat to connect to database, but database must be on before running it. Directory lib contains File hsqldb.jar . It is the database to be used by you. Running database First

How to handle values from dynamically generated elements in web page using struts2

Some time you will see the form containing the button " Add More " . This facility is provided for the user to get the values for unknown number of repeating for some information. for example when you are asking to get the projects details from user, you need to put the option to add the more project for the user since you don't known how many projects user have. In the HTML form, you repeat the particular section to get the multiple values for those elements. In Html page , you can put the option to add new row of elements or text fields by writing the java script or using JQuery API. Now, the question is that how to capture the values of dynamically generated text fields on the server. Using the servlet programming you can get the values by using getParameters() method that resultants the array of the parameter having the same name. But this limit you to naming the text fields in the HTML form. To ally this approach, you have to take the same name for t

In Process Mode of HSQLDB in web application.

If you want to use the database into your web application, you can use the HSQLDB in In_Process mode. In this mode, you can embed the HSQLDB into your web application and it runs as a part of your web application programm in the same JVM. In this mode, the database does not open any port to connect to the application on the hosing machine and you don't need to configure anything to access it. Database is not expposed to other application and can not be accessed from any dabase tools like dbVisualizer etc. In this mode ,database will be unknown from any other person except you. But in the 1.8.0 version, you can use Server intance for external as well as in process access.  To close the databse, you can issue SHUTDOWN command as an SQL query.   In the in-process mode, database starts from JDBC with the associated databse file provided through  connection URL. for example   DriverManager.getConnection("jdbc:hsqldb:mydatabase","SA","");   Here myd