Academic Tutorials



English | French | Portugese | Dutch | Italian
Google

Online

À la maison Codes sources E-Livres Téléchargements Nous contacter Au sujet de nous

HTML Tutorials
HTML Tutorial
XHTML Tutorial
CSS Tutorial
TCP/IP Tutorial
CSS 1.0
CSS 2.0
HLML
XML Tutorials
XML Tutorial
XSL Tutorial
XSLT Tutorial
DTD Tutorial
Schema Tutorial
XForms Tutorial
XSL-FO Tutorial
XML DOM Tutorial
XLink Tutorial
XQuery Tutorial
XPath Tutorial
XPointer Tutorial
RDF Tutorial
SOAP Tutorial
WSDL Tutorial
RSS Tutorial
WAP Tutorial
Web Services Tutorial
Browser Scripting
JavaScript Tutorial
VBScript Tutorial
DHTML Tutorial
HTML DOM Tutorial
WMLScript Tutorial
E4X Tutorial
Server Scripting
ASP Tutorial
PERL Tutorial
SQL Tutorial
ADO Tutorial
CVS
Python
Apple Script
PL/SQL Tutorial
SQL Server
PHP
.NET (dotnet)
Microsoft.Net
ASP.Net
.Net Mobile
C# : C Sharp
ADO.NET
VB.NET
VC++
Multimedia
SVG Tutorial
Flash Tutorial
Media Tutorial
SMIL Tutorial
Photoshop Tutorial
Gimp Tutorial
Matlab
Gnuplot Programming
GIF Animation Tutorial
Scientific Visualization Tutorial
Graphics
Web Building
Web Browsers
Web Hosting
W3C Tutorial
Web Building
Web Quality
Web Semantic
Web Careers
Weblogic Tutorial
SEO
Web Site Hosting
Domain Name
Java Tutorials
Java Tutorial
JSP Tutorial
Servlets Tutorial
Struts Tutorial
EJB Tutorial
JMS Tutorial
JMX Tutorial
Eclipse
J2ME
JBOSS
Programming Langauges
C Tutorial
C++ Tutorial
Visual Basic Tutorial
Data Structures Using C
Cobol
Assembly Language
Mainframe
Forth Programming
Lisp Programming
Pascal
Delphi
Fortran
OOPs
Data Warehousing
CGI Programming
Emacs Tutorial
Gnome
ILU
Soft Skills
Communication Skills
Time Management
Project Management
Team Work
Leadership Skills
Corporate Communication
Negotiation Skills
Database Tutorials
Oracle
MySQL
Operating System
BSD
Symbian
Unix
Internet
IP-Masquerading
IPC
MIDI
Software Testing
Testing
Firewalls
SAP Module
ERP
ABAP
Business Warehousing
SAP Basis
Material Management
Sales & Distribution
Human Resource
Netweaver
Customer Relationship Management
Production and Planning
Networking Programming
Corba Tutorial
Networking Tutorial
Microsoft Office
Microsoft Word
Microsoft Outlook
Microsoft PowerPoint
Microsoft Publisher
Microsoft Excel
Microsoft Front Page
Microsoft InfoPath
Microsoft Access
Accounting
Financial Accounting
Managerial Accounting


Produire de la réponse de serveur : Codes statut de HTTP
Previous Next




Quand un web server répond à la demande du navigateur ou de tout autre web client, la réponse se compose typiquement d'une ligne d'état, de quelques en-têtes de réponse, d'un interligne, et du document




Indication des codes statut

Comme décrit ci-dessus, la ligne d'état de réponse de HTTP comprend la version de HTTP, un code statut, et un message associé. Puisque le message est directement associé au code statut et la version de HTTP est déterminée par le serveur, tout servlet doit faire est de placer le code statut. La manière dont de faire est par la méthode de setStatus de HttpServletResponse.

La méthode de setStatus prend l'interne (le code statut) car un argument, mais au lieu d'employer des nombres explicites, il est plus clair et plus fiable pour employer les constantes définies dans HttpServletResponse. Le nom de chacun constant est dérivé du message standard de HTTP 1.1 pour chacun constant, tout majuscule avec un préfixe de Sc (pour le code statut) et d'espaces changés en soulignages. Ainsi, puisque le message pour 404 n'est pas trouvé, la constante équivalente dans le HttpServletResponse est SC_NOT_FOUND là sont deux exceptions cependant. Pour une certaine raison impaire la constante pour le code 302 n'est dérivée du message de HTTP 1.0, pas le message de HTTP 1.1, et la constante pour le code 307 est absente tout à fait.

Le réglage du code statut ne signifie pas toujours que vous n'avez pas besoin du retour un document. Par exemple, bien que la plupart des serveurs produisent du petit message non trouvé de « dossier » pour 404 réponses, les servlets pourraient vouloir adapter cette réponse. Cependant, si vous faites ceci, vous devez être sûr d'appeler response.setStatus avant d'envoyer n'importe quel contenu par l'intermédiaire de PrintWriter.

Bien que la méthode générale de placer des codes statut soit simplement à l'appel response.setStatus (interne), il y a deux cas communs où une méthode de raccourci dans le HttpServletResponse est fournie. La méthode de sendError produit de la réponse 404 avec un message court composé à l'intérieur d'un document de HTML. Et la méthode de sendRedirect produit de la réponse 302 avec un en-tête d'endroit indiquant l'URL du nouveau document.




Codes statut de HTTP 1.1 et leur signification

Suivret la liste de tous codes statut disponibles de HTTP 1.1, avec leur message et interprétation associés. Vous devriez être prudent en employant les codes statut qui sont disponibles seulement dans HTTP 1.1, puisque beaucoup de navigateurs soutiennent toujours seulement HTTP 1.0. Si vous employez les codes statut spécifiques à HTTP 1.1, dans la plupart des cas vous voulez à vérifiez explicitement la version de HTTP de la demande (par l'intermédiaire de la méthode de getProtocol de HttpServletRequest) ou la réservez pour des situations quand aucun code statut de HTTP 1.0 ne serait particulièrement signicatif au client de toute façon.

Status Code Associated Message Meaning
100 Continue Continue with partial request. (New in HTTP 1.1)
101 Switching Protocols

Server will comply with Upgrade header and change to different protocol. (New in HTTP 1.1)

200 OK

Everything's fine; document follows for GET and POST requests. This is the default for servlets; if you don't use setStatus, you'll get this.

201 Created

Server created a document; the Location header indicates its URL.

202 Accepted Request is being acted upon, but processing is not completed.
203 Non-Authoritative Information Document is being returned normally, but some of the response headers might be incorrect since a document copy is being used. (New in HTTP 1.1)
204 No Content

No new document; browser should continue to display previous document. This is a useful if the user periodically reloads a page and you can determine that the previous page is already up to date. However, this does not work for pages that are automatically reloaded via the Refresh response header or the equivalent <META HTTP-EQUIV="Refresh" ...> header, since returning this status code stops future reloading. JavaScript-based automatic reloading could still work in such a case, though.

205 Reset Content

No new document, but browser should reset document view. Used to force browser to clear CGI form fields. (New in HTTP 1.1)

206 Partial Content

Client sent a partial request with a Range header, and server has fulfilled it. (New in HTTP 1.1)

300 Multiple Choices

Document requested can be found several places; they'll be listed in the returned document. If server has a preferred choice, it should be listed in the Location response header.

301 Moved Permanently

Requested document is elsewhere, and the URL for it is given in the Location response header. Browsers should automatically follow the link to the new URL.

302 Found

Similar to 301, except that the new URL should be interpreted as a temporary replacement, not a permanent one. Note: the message was "Moved Temporarily" in HTTP 1.0, and the constant in HttpServletResponse is SC_MOVED_TEMPORARILY, not SC_FOUND.Very useful header, since browsers automatically follow the link to the new URL. This status code is so useful that there is a special method for it, sendRedirect. Using response.sendRedirect(url) has a couple of advantages over doing response.setStatus(response.SC_MOVED_TEMPORARILY) and response.setHeader("Location", url). First, it is easier. Second, with sendRedirect, the servlet automatically builds a page containing the link (to show to older browsers that don't automatically follow redirects). Finally, sendRedirect can handle relative URLs, automatically translating them to absolute ones.

Note that this status code is sometimes used interchangeably with 301. some servers will send 301 and others will send 302.

Technically, browsers are only supposed to automatically follow the redirection if the original request was GET. See the 307 header for details.

303 See Other

Like 301/302, except that if the original request was POST, the redirected document (given in the Location header) should be retrieved via GET. (New in HTTP 1.1)

304 Not Modified

Client has a cached document and performed a conditional request (usually by supplying an If-Modified-Since header indicating that it only wants documents newer than a specified date). Server wants to tell client that the old, cached document should still be used.

305 Use Proxy

Requested document should be retrieved via proxy listed in Location header. (New in HTTP 1.1)

307 Temporary Redirect

This is identical to 302 ("Found" or "Temporarily Moved"). It was added to HTTP 1.1 since many browsers erroneously followed the redirection on a 302 response even if the original message was a POST, even though it really ought to have followed the redirection of a POST request only on a 303 response. This response is intended to be unambigously clear: follow redirected GET and POST requests in the case of 303 responses, only follow the redirection for GET requests in the case of 307 responses. Note: for some reason there is no constant in HttpServletResponse corresponding to this status code. (New in HTTP 1.1)

400 Bad Request Bad syntax in the request.
401 Unauthorized

Client tried to access password-protected page without proper authorization. Response should include a WWW-Authenticate header that the browser would use to pop up a username/password dialog box, which then comes back via the Authorization header.

403 Forbidden

Resource is not available, regardless of authorization. Often the result of bad file or directory permissions on the server.

404 Not Found

No resource could be found at that address. This is the standard "no such page" response. This is such a common and useful response that there is a special method for it in HttpServletResponse: sendError(message). The advantage of sendError over setStatus is that, with sendError, the server automatically generates an error page showing the error message.

405 Method Not Allowed The request method (GET, POST, HEAD, DELETE, PUT, TRACE, etc.) was not allowed for this particular resource. (New in HTTP 1.1)
406 Not Acceptable

Resource indicated generates a MIME type incompatible with that specified by the client via its Accept header. (New in HTTP 1.1)

407 Proxy Authentication Required Similar to 401, but proxy server must return a Proxy-Authenticate header. (New in HTTP 1.1)
408 Request Timeout The client took too long to send the request. (New in HTTP 1.1)
409 Conflict

Usually associated with PUT requests; used for situations such as trying to upload an incorrect version of a file. (New in HTTP 1.1)

410 Gone

Document is gone; no forwarding address known. Differs from 404 in that the document is is known to be permanently gone in this case, not just unavailable for unknown reasons as with 404. (New in HTTP 1.1)

411 Length Required

Server cannot process request unless client sends a Content-Length header. (New in HTTP 1.1)

412 Precondition Failed

Some precondition specified in the request headers was false. (New in HTTP 1.1)

413 Request Entity Too Large

The requested document is bigger than the server wants to handle now. If the server thinks it can handle it later, it should include a Retry-After header. (New in HTTP 1.1)

414 Request URI Too Long The URI is too long. (New in HTTP 1.1)
415 Unsupported Media Type Request is in an unknown format. (New in HTTP 1.1)
416 Requested Range Not Satisfiable Client included an unsatisfiable Range header in request. (New in HTTP 1.1)
417 Expectation Failed

Value in the Expect request header could not be met. (New in HTTP 1.1)

500 Internal Server Error

Generic "server is confused" message. It is often the result of CGI programs or (heaven forbid!) servlets that crash or return improperly formatted headers.

501 Not Implemented

Server doesn't support functionality to fulfill request. Used, for example, when client issues command like PUT that server doesn't support.

502 Bad Gateway

Used by servers that act as proxies or gateways; indicates that initial server got a bad response from the remote server.

503 Service Unavailable

Server cannot respond due to maintenance or overloading. For example, a servlet might return this header if some thread or database connection pool is currently full. Server can supply a Retry-After header.

504 Gateway Timeout

Used by servers that act as proxies or gateways; indicates that initial server didn't get a response from the remote server in time. (New in HTTP 1.1)

505 HTTP Version Not Supported

Server doesn't support version of HTTP indicated in request line. (New in HTTP 1.1)





Previous Next

Keywords: Handling the Client Request:Form Data,asp net client,asp net data,vb net data,control data,data net,java client,data repeater


HTML Quizes
HTML Quiz
XHTML Quiz
CSS Quiz
TCP/IP Quiz
CSS 1.0 Quiz
CSS 2.0 Quiz
HLML Quiz
XML Quizes
XML Quiz
XSL Quiz
XSLT Quiz
DTD Quiz
Schema Quiz
XForms Quiz
XSL-FO Quiz
XML DOM Quiz
XLink Quiz
XQuery Quiz
XPath Quiz
XPointer Quiz
RDF Quiz
SOAP Quiz
WSDL Quiz
RSS Quiz
WAP Quiz
Web Services Quiz
Browser Scripting Quizes
JavaScript Quiz
VBScript Quiz
DHTML Quiz
HTML DOM Quiz
WMLScript Quiz
E4X Quiz
Server Scripting Quizes
ASP Quiz
PERL Quiz
SQL Quiz
ADO Quiz
CVS Quiz
Python Quiz
Apple Script Quiz
PL/SQL Quiz
SQL Server Quiz
PHP Quiz
.NET (dotnet) Quizes
Microsoft.Net Quiz
ASP.Net Quiz
.Net Mobile Quiz
C# : C Sharp Quiz
ADO.NET Quiz
VB.NET Quiz
VC++ Quiz
Multimedia Quizes
SVG Quiz
Flash Quiz
Media Quiz
SMIL Quiz
Photoshop Quiz
Gimp Quiz
Matlab Quiz
Gnuplot Programming Quiz
GIF Animation Quiz
Scientific Visualization Quiz
Graphics Quiz
Web Building  Quizes
Web Browsers Quiz
Web Hosting Quiz
W3C Quiz
Web Building Quiz
Web Quality Quiz
Web Semantic Quiz
Web Careers Quiz
Weblogic Quiz
SEO Quiz
Web Site Hosting Quiz
Domain Name Quiz
Java Quizes
Java Quiz
JSP Quiz
Servlets Quiz
Struts Quiz
EJB Quiz
JMS Quiz
JMX Quiz
Eclipse Quiz
J2ME Quiz
JBOSS Quiz
Programming Langauges Quizes
C Quiz
C++ Quiz
Visual Basic Quiz
Data Structures Using C Quiz
Cobol Quiz
Assembly Language Quiz
Mainframe Quiz
Forth Programming Quiz
Lisp Programming Quiz
Pascal Quiz
Delphi Quiz
Fortran Quiz
OOPs Quiz
Data Warehousing Quiz
CGI Programming Quiz
Emacs Quiz
Gnome Quiz
ILU Quiz
Soft Skills Quizes
Communication Skills Quiz
Time Management Quiz
Project Management Quiz
Team Work Quiz
Leadership Skills Quiz
Corporate Communication Quiz
Negotiation Skills Quiz
Database Quizes
Oracle Quiz
MySQL Quiz
Operating System Quizes
BSD Quiz
Symbian Quiz
Unix Quiz
Internet Quiz
IP-Masquerading Quiz
IPC Quiz
MIDI Quiz
Software Testing Quizes
Testing Quiz
Firewalls Quiz
SAP Module Quizes
ERP Quiz
ABAP Quiz
Business Warehousing Quiz
SAP Basis Quiz
Material Management Quiz
Sales & Distribution Quiz
Human Resource Quiz
Netweaver Quiz
Customer Relationship Management Quiz
Production and Planning Quiz
Networking Programming Quizes
Corba Quiz
Networking Quiz
Microsoft Office Quizes
Microsoft Word Quiz
Microsoft Outlook Quiz
Microsoft PowerPoint Quiz
Microsoft Publisher Quiz
Microsoft Excel Quiz
Microsoft Front Page Quiz
Microsoft InfoPath Quiz
Microsoft Access Quiz
Accounting Quizes
Financial Accounting Quiz
Managerial Accounting Quiz

Privacy Policy
Copyright © 2003-2021 Vyom Technosoft Pvt. Ltd., All Rights Reserved.