Handling IIS low level errors - iis

I am using IIS8 with MVC.NET website built on .net framework 4.5, Here as a part of security fix I am told to have the generic error message for all 403 status codes, This I was able to achieve using httpErrors tags from web.config file using "" entry. But there are some error which are thrown by http.sys which are still showing the system level errors instead of generic error. For example doing a GET request to url "http://abc.xyz.com/login/../../../../../../../admin.txt" is returning "HTTP Error 403. The request URL is forbidden." error while it should return the generic error message which is mentioned in my httpErrors tag.
To my surprise if I stop the website (Not IIS) still I am getting the same error which did confirm that the error is handleded at the low level APIs of IIS and not getting passed down to application layer hence any changes in web.config are not helping to fix this issue.
Could someone please shade some light on how to fix this issue ?
Thanks
Ajay Sawant

Related

IIS error 403 not logged and showing unknown error page

When I try to access a page on my IIS web I get an error 403. The error is not logged to the log file and the error page shown is not the one that's defined in the config.
That's the content of the error page:
<html><head><title>403 Forbidden</title></head><body>Access denied</body>
Can anyone help me to find this error page and get the error logged?
The 403 Forbidden error is an HTTP status code that means that accessing the page or directory you were trying to reach is absolutely forbidden for some reason.
To resolve this issue, you need to enable directory browsing for your application. To enable directory browsing on IIS, check out the steps from this Microsoft document.
If you still can’t solve the problem, you can use failed request tracking to view detailed error information.

/CMSPages/PortalTemplate.aspx throws 404 errors but site still works fine

I have a situation here, on iis logs I see the /CMSPages/PortalTemplate.aspx causing 404 errors but the requests are still fulfilled.
The question that I have is how do I stop these 404 errors from being logged since the website still works. I only want to see the real 404 erros which occur when the request URL is invalid
I am using the Portal Engine approach
In the IIS log, find out what the parameters after the /CMSPages/PortalTemplate.aspx causing the 404. You may be able to see these 404 errors in the Kentico Event Log as well. The majority of the requests to deliver page content goes through the /CMSPages/PortalTemplate.aspx page which is why you're seeing it in the IIS logs.
Once you find the record which has the 404 info, you should be able to find the path to the file and resolve it.
Check your network tab in your favorite browser. Usually there is a favicon or woff font not being served.

IIS 7.5 HTTP Error 500.19 - Internal Server Error. Live website is functioning but has a /test url unknown to our developers which gives error 500.19

I am an intern in an interactive media company, my employers have many websites they host for small businesses. When any of the websites URL's is accessed on the web it works great, altough when you place "/test" behind the url and enter it comes up with the 500.19 internal server error, stating the configuration file path is invalid. While it should just be giving the 404 error.
We did not create the /test site. We also have URL rewrite installed and functioning but we really need to know what is causing this error. As I said it needs to give a 404 error and than perhaps we can have it rewrite this URL.
If anyone has any idea what is going on here please help. Searching the web has yielded zero results. Below I will paste the full error report.
Error Summary
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070003
Config Error Cannot read configuration file
Config File \\?\D:\Sites\vhosts\***********.com\httpdocs\test\web.config
Requested URL http://***.*************.com:80/test
Physical Path D:\Sites\vhosts\************.com\httpdocs\test
Logon Method Not yet determined
Logon User Not yet determined
Config Source
-1:
0:

How to display an error page for static files when using existingResponse="PassThrough" in IIS 7

To be able to get my application (Umbraco CMS) to handle 404 errors, I need to have following setting in my web.config:
<httpErrors existingResponse="PassThrough" />
It works well for displaying a custom 404 error page from Umbraco, but it doesn't work for displaying a 404 error page when a static file cant be found.
For example http://www.example.com/non-existing-file.png returns a 404 status code, but respons is blank. That fits with this description of the PassThrough mode:
PassThrough – If existingResponse is seen as “PassThrough”, custom
error module will always pass through responses from modules. This
setting will make custom error module return blank response if modules
don’t set any text.
(http://blogs.iis.net/ksingla/archive/2008/02/18/what-to-expect-from-iis7-custom-error-module.aspx)
What is the "custom error module"? And how do I get it to return a non blank response?
Update
After stepping through the request handling routines in Umbraco (with a debugger), I have a better understanding of the problem space. As written in the citation above, when existingResponse="PassThrough" then all handling of http errors is done in the custom modules. So to answer my own question, a "custom error module" is in this instance the "UmbracoModule".
One way to solve this problem would be to create a new custom module that will check for the existence of the static files on the disk. It can be done quite nice, I read the list of static files from IIS and read the configuration of customErrors or httpErrors elements from the web.config to get a custom error page. But I kind of think this is crude solution. I would much rather pass the responsibility back to IIS.
Any ideas?
You're correct. For the benefit of anyone else looking for help with this, here's some extra information on 404 handling.
Old Umbraco wiki page - describes your solution using the file /config/umbracoSettings.config
404 for files - works for Umbraco 7 and describes the use of the tag <httpErrors/>
IIS version 6 fix - fixing on IIS6 and how it compares with IIS7

iis error 500.19 ,the related configuration data for the page is invalid

After publishing the solution when i tried to access my home page im getting the following error.Its working localy in my system but when i tried to publish it im getting the following error.
Kindly reply as early as possible because im in a precaurious situation now

Resources