My Apache log frequently contains message such as "File does not exist". I have a page named 404.shtml and when I try to receive a Invalid page, the contents of 404.shtml are displayed. But at the same time the invalid page url is also written in the logs.
Is is possible avoid such errors within the Apache log, As sometimes the log is flooded with such entries
Related
I read about a lot of ideas about how to test the ErrorDocument 500 directive, but they don't work. If I put bad php code, I still get a page with my php error in it. If I create a bad htaccess file, I get the following error and not my custom error :
[an error occurred while processing this directive] The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there was an error in a CGI script. [an error occurred while processing this directive]
I need to raise this custom error page to ensure that it works even though most applications will manage their own 500 pages.
Thanks
PHP errors aren't 500 errors. Apache is fine. PHP has encountered the error. This can be hidden in PHP.ini, but it results in a "white screen of death" instead.
On to the .htaccess problem. The .htaccess file controls the custom error pages for your site. If Apache cannot parse the custom error pages in this file it means there are no custom error pages set to display.
I have an Apache Web Server in front of a JBOSS app server. I have configured the ErrorDocument (with all the HTTP error codes) in Apache to return a fixed string of "There is an error".
Accessing the application is via the Apache Web Server, to the JBOSS app server.
However, when an error code of 404 throws from the JBOSS server, this Apache server did not catch the error and did not display the "There is an error", instead, the error page of JBOSS is served to the end user.
I have checked the log of Apache and can see the HTTP error code.
Can someone advise me what am I doing wrong or any additional config is needed?
Thanks and regards,
Jacky
There are three ways to display the custom HTTP error messages.
output a customized message
ErrorDocument 403 "There is an error"
internally redirect to a local URL-path to handle the error
ErrorDocument 404 /errorDocs/404.html
redirect to an external URL to handle the problem/error
ErrorDocument 404 http://example.com/cgi-bin/server-error.cgi
Please check if it is happening on all 404 scenarios and on all browsers.
I hope you are trying the method 1 and it is very straightforward one, scope of this directive is server config, virtual host, directory, .htaccess. If the configuration file is updated as mentioned, it must work.
These could be the situations,
ensure the text to be displayed is wrapped in quotes (") if it consists of more than one word.
Microsoft Internet Explorer (MSIE) will by default ignore server-generated error messages when they are "too small" and substitute its own "friendly" error messages. The size threshold varies depending on the type of error, but in general, if you make your error document greater than 512 bytes, then MSIE will show the server-generated error rather than masking it.
Although most error messages can be overridden, there are certain circumstances where the internal messages are used regardless of the setting of ErrorDocument. In particular, if a malformed request is detected, normal request processing will be immediately halted and the internal error message returned. This is necessary to guard against security problems caused by bad requests.
Reference
I came across 404 error a few times and i have difficulties in debugging this kind of problem.
What is the strategy and tools available to analyse such problems (firebug, logs...).
How to differentiate and fix the cause ?
page not existing ,wrong path , redirection and rewriting ,server problem ...
404 error code means that a file is not found for whatever reason.
Just check that the file exists and that the path you use is right.
You can analyse sent requests and received responses headers and body in your browser's developper console if you want more details about why some request failed.
We are seeing intermittent (not all jobs fail) Backend errors when attempting to create a table from a JSON file in GS from the Browser UI.
There is only a red pop up with the "Backend Error" message, no other information and it goes away after a few seconds.
How can we troubleshoot or gather additional information about this error?
I've seen hundreds of pages explaining how to create custom error pages in Apache 2 server. My question is different. I have a web application running in Apache (it is a ISAPI DLL, but it could also be a CGI executable). My application can handle internal server errors and generate a detailed error message (for instance, include a full stack trace), included in the response together with error code 500. AFAIK, Apache just let me use redirection in order to display custom error messages: http://httpd.apache.org/docs/2.2/custom-error.html
HTTP spec (RFC 2616 - section 10), not only allows but also recommend that detailed error message should be included in the BODY section of the response in case of error code > 500.
Link: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5
Seems that Apache won't let my custom error message go to the browser, and always replace it with its own internal error message and I believe that it is not the correct behavior, based on RFC 2616.
So my question is: Is there any setting in Apache server that will let my custom message go to the browser? Or, is there anything that can be done in my application that will instruct Apache to send my custom error message (something like some specific header field in the response)?
More on the subject:
When my ISAPI application returns error code 500, with other error information in the response body, Apache replaces it with its standard "500 Internal Server Error" message/HTML content, and inside Error.log file I can see the "useless" "Premature end of script headers" message. I'm deeply sure that my headers are fine, including the Content-Type field.
If I replace the 500 error code with any other server error code (e.g. 501) it works flawlessly and my response goes to the browser as is. The same header is sent to the Apache server, only the error code is different (501, instead of 500). With this test result in mind, one of these two must be true:
1- Apache requires some specific header field when status code is 500
2- Apache won't let custom error messages with status code 500 go to the browser.
I don't see any other alternative.
I think you're conflating two questions. You can generate a 500 response with a CGI script and include your custom body. Or you can override any 500 with any resource you want.
If you're failing to do the former, it's likely because of some subtle thing in the ISAPI interface between Apache and your module. Desk-checking the code says you should be able either set the pseudo
Status: 500
Header, or basically return any ISAPI error and end up with a 500 and your custom body.
Apache has two notions of a status code -- the one in the status line (r->status) and an error code returned separately from the module that handles the request (return HTTP_INTERNAL_SERVER_ERROR, return r->status).
When the former is used as the latter is when the custom error messages get lost. All of that happens in./modules/arch/win32/mod_isapi.c in Apache. Whatever is going on, it is ISAPI unique.