| Http Response codes as specified in Servlet API (www.sun.java) |
CODE | DISCRIPTION |
100 | Indicating the client can continue. |
101 | Indicating the server is switching protocols according to Upgrade header. |
200 | Indicating the request succeeded normally. |
201 | Indicating the request succeeded and created a new resource on the server. |
202 | Indicating that a request was accepted for processing, but was not completed. |
203 | Indicating that the meta information presented by the client did not originate from the server. |
204 | Indicating that the request succeeded but that there was no new information to return. |
205 | Indicating that the agent SHOULD reset the document view which caused the request to be sent. |
206 | Indicating that the server has fulfilled the partial GET request for the resource. |
300 | Indicating that the requested resource corresponds to any one of a set of representations, each with its own specific location. |
301 | Indicating that the resource has permanently moved to a new location, and that future references should use a new URI with their requests. |
302 | Indicating that the resource reside temporarily under a different URI. |
303 | Indicating that the response to the request can be found under a different URI. |
304 | Indicating that a conditional GET operation found that the resource was available and not modified. |
305 | Indicating that the requested resource MUST be accessed through the proxy given by the Location field. |
307 | Indicating that the requested resource resides temporarily under a different URI. |
400 | Indicating the request sent by the client was syntactically incorrect. |
401 | Indicating that the request requires HTTP authentication. |
402 | Reserved for future use. |
403 | Indicating the server understood the request but refused to fulfill it. |
404 | Indicating that the requested resource is not available. |
405 | 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) |
406 | 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. |
407 | Indicating that the client MUST first authenticate itself with the proxy. |
408 | Indicating that the client did not produce a request within the time that the server was prepared to wait. |
409 | Indicating that the request could not be completed due to a conflict with the current state of the resource. |
410 | Indicating that the resource is no longer available at the server and no forwarding address is known. |
411 | Indicating that the request cannot be handled without a defined Content-Length. |
412 | Indicating that the precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. |
413 | 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. |
414 | Indicating that the server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. |
415 | 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. |
416 | Indicating that the server cannot serve the requested byte range. |
417 | Indicating that the server could not meet the expectation given in the Expect request header. |
500 | Indicating an error inside the HTTP server which prevented it from fulfilling the request. |
501 | Indicating the HTTP server does not support the functionality needed to fulfill the request. |
502 | Indicating that the HTTP server received an invalid response from a server it consulted when acting as a proxy or gateway. |
503 | Indicating that the HTTP server is temporarily overloaded, and unable to handle the request. |
504 | Indicating that the server did not receive a timely response from the upstream server while acting as a gateway or proxy. |
505 | Indicating that the server does not support or refuses to support the HTTP protocol version that was used in the request message. |
Status codes from return from server
Subscribe to:
Post Comments (Atom)
Popular Posts
-
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 ...
-
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 HSQLD...
-
HTML Page < html > < head > < title > welcome </ title > < script language = "javascript"...
-
Spring MVC provides support for processing the form as well as server side validation. It maps request parameters to form backing bean and ...
-
Some time you will see the form containing the button " Add More " . This facility is provided for the user to get the values ...
-
JSP code <%@page import="java.sql.*"%> <%! int prod_id=1; String prod_name="Laptop"; int qty=2; float p...
-
In web application ApplicationContext is created using Context Loaders. there are two implementations of context loader. ContextLoaderLis...
-
Hibernate ORM framework does not provide any approch to connect to MS Access database. Unfortunately, Access is not supported officially...
-
package process; import javax.swing. * ; import javax.swing.table. * ; import java.sql. * ; /** * This class create JTable from Da...
-
Using " mappedBy " attribute of mapping annotations(like @OneToOne, @OneToMany, @ManyToMany) for bi-directional relationship. This...

No comments:
Post a Comment