Httpd Error Codes
Contents |
response. 10.1 Informational 1xx This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this
Http Code 403
class of status code. Since HTTP/1.0 did not define any 1xx status codes, servers http code 302 MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A client MUST be prepared to accept
Http Error Wordpress
one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies http status codes cheat sheet MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) 10.1.1 100 Continue The client SHOULD continue with its request. This interim response is used to inform http response example the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. 10.1.2 101 Switching Protocols The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol might be advantageous when delivering resources that use such features. 10.2 Successful 2xx This class of status code indicates that the client's request was successfully received, understood, and accepted. 10.2.1 200 OK The request has succeeded. The information returned with the response is dep
sections of messages Error, Forward and redirection responses may be used to contain human-readable diagnostic information. Success 2xx These codes indicate success. The body section if present is the
Http Error 500 Wordpress
object returned by the request. It is a MIME format object. It is http 422 in MIME format, and may only be in text/plain, text/html or one fo the formats specified as acceptable in the request.
Http 502
OK 200 The request was fulfilled. CREATED 201 Following a POST command, this indicates success, but the textual part of the response line indicates the URI by which the newly created document should be https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html known. Accepted 202 The request has been accepted for processing, but the processing has not been completed. The request may or may not eventually be acted upon, as it may be disallowed when processing actually takes place. there is no facility for status returns from asynchronous operations such as this. Partial Information 203 When received in the response to a GET command, this indicates that the returned metainformation https://www.w3.org/Protocols/HTTP/HTRESP.html is not a definitive set of the object from a server with a copy of the object, but is from a private overlaid web. This may include annotation information about the object, for example. No Response 204 Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time. Error 4xx, 5xx The 4xx codes are intended for cases in which the client seems to have erred, and the 5xx codes for the cases in which the server is aware that the server has erred. It is impossible to distinguish these cases in general, so the difference is only informational. The body section may contain a document describing the error in human readable form. The document is in MIME format, and may only be in text/plain, text/html or one for the formats specified as acceptable in the request. Bad request 400 The request had bad syntax or was inherently impossible to be satisfied. Unauthorized 401 The parameter to this message gives a specification of authorization schemes which are acceptable. The client should retry the request
generic error responses in the event of 4xx or 5xx HTTP status codes, these responses are rather stark, uninformative, and can be intimidating to site https://httpd.apache.org/docs/2.4/custom-error.html users. You may wish to provide custom error responses which are either friendlier, or in some language other than English, or perhaps which are styled more in line with your site layout. Customized error http://www.centos.org/forums/viewtopic.php?t=56679 responses can be defined for any HTTP status code designated as an error condition - that is, any 4xx or 5xx status. Additionally, a set of values are provided, so that the error document http code can be customized further based on the values of these variables, using Server Side Includes. Or, you can have error conditions handled by a cgi program, or other dynamic handler (PHP, mod_perl, etc) which makes use of these variables. Configuration Available Variables Customizing Error Responses Multi Language Custom Error Documents See alsoComments Configuration Custom error documents are configured using the ErrorDocument directive, which may be used in httpd error codes global, virtualhost, or directory context. It may be used in .htaccess files if AllowOverride is set to FileInfo. ErrorDocument 500 "Sorry, our script crashed. Oh dear" ErrorDocument 500 /cgi-bin/crash-recover ErrorDocument 500 http://error.example.com/server_error.html ErrorDocument 404 /errors/not_found.html ErrorDocument 401 /subscription/how_to_subscribe.html The syntax of the ErrorDocument directive is: ErrorDocument <3-digit-code>
httpd General support questions Post Reply Print view Search Advanced search 15 posts 1 2 Next sadue Posts: 55 Joined: 2016/01/08 19:08:26 Unable to start/restart httpd Quote Postby sadue » 2016/03/01 11:32:37 Hey guysI tried to restart my apache httpd afetr installing php56u from ius, and php56u-cli, but I got the following error message~]$ sudo systemctl restart httpd.serviceJob for httpd.service failed because the control process exited with error code. See "systemctl status httpd.service" and "journalctl -xe" for details.Then I run the code as instructed on the error message as follows, and it generates the following message.~]$ systemctl status httpd.serviceā httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2016-03-01 11:53:07 UTC; 15s ago Docs: man:httpd(8) man:apachectl(8) Process: 28473 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE) Process: 28471 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE) Main PID: 28471 (code=exited, status=1/FAILURE)Mar 01 11:53:07 myclasslist systemd[1]: Starting The Apache HTTP Server...Mar 01 11:53:07 myclasslist httpd[28471]: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf...nfigMar 01 11:53:07 myclasslist systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILUREMar 01 11:53:07 myclasslist kill[28473]: kill: cannot find process ""Mar 01 11:53:07 myclasslist systemd[1]: httpd.service: control process exited, code=exited status=1Mar 01 11:53:07 myclasslist systemd[1]: Failed to start The Apache HTTP Server.Mar 01 11:53:07 myclasslist systemd[1]: Unit httpd.service entered failed state.Mar 01 11:53:07 myclasslist systemd[1]: httpd.service failed.Hint: Some lines were ellipsized, use -l to show in full.Please guys, what should I do? Top stevemowbray Posts: 209 Joined: 2012/06/26 14:20:47 Re: Unable to start/restart httpd Quote Postby stevemowbray » 2016/03/01 12:11:14 You need to fix the syntax error on line 353 of your config file. Top sadue Posts: 55 Joined: 2016/01/08 19:08:26 Re: Unable to start/restart httpd Quote Postby sadue » 2016/03/08 15:14:34 Okay.I rebuild and start everything all afresh.I now tried to enable virtualhost following the bellow procedure which is to include sslsudo mkdir -p /var/www/mydomain.org/htdocssudo chown -R apache:apache /var/www/mydomain